moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-28 04:02:20 -05:00
Code Issues Releases Wiki Activity

1.1rc2

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3649 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-11-20 00:50:07 +00:00
parent b564bcb3bc
commit 3656b40695
1 changed files with 25 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
xep-0167.xml
View File

@ -42,10 +42,10 @@
&robmcqueen;
&diana;
<revision>
<version>1.1rc1</version>
<date>in progress, last updated 2009-11-08</date>
<version>1.1rc2</version>
<date>in progress, last updated 2009-11-19</date>
<initials>psa</initials>
<remark><p>Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination.</p></remark>
<remark><p>Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of &lt;failed-application/&gt; and a list of the supported codecs.</p></remark>
</revision>
<revision>
<version>1.0</version>
@ -496,7 +496,7 @@ Initiator Responder
</jingle>
</iq>
]]></example>
<p>Note: If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of &lt;failed-application/&gt;. This reason can also be included in non-termination events, such as content-reject when the other party has tried to add a content-type for which the recipient supports none of the payload types.</p>
<p>If the responder supports none of the payload-types offered by the initiator, the responder SHOULD terminate the session and include a Jingle reason of &lt;failed-application/&gt;.</p>
<p>If the responder accepts the session, the initiator acknowledges the session-accept message:</p>
<example caption="Initiator acknowledges session acceptance"><![CDATA[
<iq from='romeo@montague.lit/orchard'
@ -1515,7 +1515,27 @@ Romeo Juliet
to='juliet@capulet.lit/balcony'
type='result'/>
]]></example>
<p>Then Juliet accepts video.</p>
<p>Note: If the responder supports none of the payload-types offered by the initiator, the responder MUST reply to the content-add request with a content-reject; this message SHOULD include a Jingle reason of &lt;failed-application/&gt; and a list of the payload-types that the responder supports (along with an empty element for the same transport offered by the initiatior), as shown in the following example.</p>
<example caption="Alternate flow: responder sends content-reject"><![CDATA[
<iq from='juliet@montague.lit/balcony'
id='vx2s91a6'
to='romeo@montague.lit/orchard'
type='set'>
<jingle xmlns='urn:xmpp:jingle:1'
action='content-reject'
initiator='romeo@montague.lit/orchard'
sid='a73sjjvkla37jfea'>
<content creator='initiator' name='webcam'>
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='video'>
<payload-type id='101' name='H263-1998' clockrate='90000'/>
<payload-type id='102' name='H263-2000' clockrate='90000'/>
</description>
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
</content>
</jingle>
</iq>
]]></example>
<p>However, here we assume that Juliet's client supports at least one of the payload-types offered by Romeo's client, and that she Juliet accepts the offer of adding video to the session.</p>
<example caption="Responder accepts additional content-type"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
id='ih481v7s'