diff --git a/xep-0167.xml b/xep-0167.xml index 7eb1c1ab..8c029f2c 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -647,7 +647,7 @@ delivery-method=inline; configuration=somebase16string;

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. A <trying/> element (equivalent to the SIP 100 Trying response code) is not necessary, since each session-level message is acknowledged via XMPP IQ semantics.

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).

-

The <active/> 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 <active/> 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.

+

The <active/> 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 <active/> element applies to all aspects of the session, and thus does not possess a 'name' attribute.

- + ]]> @@ -2036,19 +2035,19 @@ Romeo Juliet xmlns='urn:xmpp:jingle:apps:rtp:info:1' elementFormDefault='qualified'> - + - + - + - + - + - +