From b5f195594a9fb1428498b7ee11f2502b6de4c1fb Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 7 Dec 2007 00:02:58 +0000 Subject: [PATCH] 0.13 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1459 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0167.xml | 126 ++++++++++++++++++++++++++------------------------- 1 file changed, 65 insertions(+), 61 deletions(-) diff --git a/xep-0167.xml b/xep-0167.xml index 42227321..4380f2b5 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -25,6 +25,12 @@ &stpeter; &seanegan; &robmcqueen; + + 0.13 + 2007-12-06 + psa +

To track changes to XEP-0166, modified busy scenario and removed unsupported-codecs error.

 + 0.12 2007-11-27 @@ -243,18 +249,7 @@ ]]> -

Upon receiving the session-initiate stanza, the responder determines whether it can proceed with the negotiation. The general Jingle error cases are specified in XEP-0166 and illustrated in the Scenarios section of this document. In addition, the responder must determine if it supports any of the payload types advertised by the initiator; if it supports none of the offered payload types, it must reject the session by returning a ¬acceptable; error with a Jingle-Audio-specific condition of <unsupported-codecs/>:

- - - - - - - ]]> +

Upon receiving the session-initiate stanza, the responder determines whether it can proceed with the negotiation. The general Jingle error cases are specified in XEP-0166 and illustrated in the Scenarios section of this document.

If there is no error, the responder acknowledges the session initiation request.

- -

The Jingle-Audio-specific error conditions are as follows:

- - - - - - - - - - - -
Jingle Audio ConditionXMPP ConditionDescription
<unsupported-codecs/>¬acceptable;The recipient does not support any of the offered audio encodings.
- -

If an entity supports Jingle audio exchanges via RTP, it MUST advertise that fact by returning a feature of "http://www.xmpp.org/extensions/xep-0167.html#ns" &NSNOTE; in response to &xep0030; information requests.

| - | error | - | (recipient-unavailable) | + | ack | |<----------------------------| + | session-info (ringing) | + |<----------------------------| + | ack | + |---------------------------->| + | terminate | + | (reasoncode = busy) | + |<----------------------------| + | ack | + |---------------------------->| + | | ]]>

The protocol flow is as follows.

]]> - - - - - + type='result'/> + ]]> + + + + ]]> + + ]]> + + + + ]]> +

The other party then acknowledges termination of the session:

+ + ]]>

In this scenario, Romeo initiates a voice chat with Juliet using a transport method of ICE-UDP. The parties also exchange informational messages.

@@ -780,7 +802,8 @@ Romeo Juliet ]]> @@ -1101,7 +1124,8 @@ Romeo Juliet ]]> @@ -1287,7 +1311,8 @@ Romeo Juliet ]]> @@ -1400,27 +1425,6 @@ Romeo Juliet - - ]]> - - - - - - - - - - - - - - ]]>