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

correction to active element 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3095 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-04-27 13:19:39 +00:00
parent b562806174
commit 7578c88c92
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
xep-0167.xml
View File

@ -647,7 +647,7 @@ delivery-method=inline; configuration=somebase16string;
<p>Informational messages can be sent by either party within the context of Jingle to communicate the status of a Jingle RTP session, device, or principal. The informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element qualified by the 'urn:xmpp:jingle:apps:rtp:info:1' namespace. The following payload elements are defined. <note>A &lt;trying/&gt; element (equivalent to the SIP 100 Trying response code) is not necessary, since each session-level message is acknowledged via XMPP IQ semantics.</note></p>
<p>Note: Because an informational message is sent in an IQ-set, the receiving party MUST return either an IQ-result or an IQ-error (normally an IQ-result simply to acknowledge receipt).</p>
<section2 topic='Active' anchor='info-active'>
<p>The &lt;active/&gt; payload indicates that the principal or device is again actively participating in the session after having been on mute or having put the other party on hold. The &lt;active/&gt; element MAY possess a 'name' attribute whose value specifies a particular session that is again active (e.g., activating the video aspect but not the audio aspect of a voice+video chat). If no 'name' attribute is included, the recipient MUST assume that all sessions are active.</p>
<p>The &lt;active/&gt; payload indicates that the principal or device is again actively participating in the session after having been on mute or having put the other party on hold. The &lt;active/&gt; element applies to all aspects of the session, and thus does not possess a 'name' attribute.</p>
<example caption="Responder sends active message"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
id='yh3gr714'
@ -657,8 +657,7 @@ delivery-method=inline; configuration=somebase16string;
action='session-info'
initiator='romeo@montague.lit/orchard'
sid='a73sjjvkla37jfea'>
<active xmlns='urn:xmpp:jingle:apps:rtp:info:1'
name='webcam'/>
<active xmlns='urn:xmpp:jingle:apps:rtp:info:1'/>
</jingle>
</iq>
]]></example>
@ -2036,19 +2035,19 @@ Romeo Juliet
xmlns='urn:xmpp:jingle:apps:rtp:info:1'
elementFormDefault='qualified'>
<xs:element name='active' type='actionElementType'/>
<xs:element name='active' type='empty'/>
<xs:element name='hold' type='actionElementType'/>
<xs:element name='hold' type='empty'/>
<xs:element name='mute' type='actionElementType'/>
<xs:element name='mute' type='mutingElementType'/>
<xs:element name='ringing' type='empty'/>
<xs:element name='unhold' type='actionElementType'/>
<xs:element name='unhold' type='empty'/>
<xs:element name='unmute' type='actionElementType'/>
<xs:element name='unmute' type='mutingElementType'/>
<xs:complexType name='actionElementType'>
<xs:complexType name='mutingElementType'>
<xs:simpleContent>
<xs:extension base='empty'>
<xs:attribute name='name'