To track changes to XEP-0166, modified busy scenario and removed unsupported-codecs error.
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 Condition | -XMPP Condition | -Description | -
---|---|---|
<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.
The protocol flow is as follows.
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
-
-
-
-
-
-
-
-
-
-
-
]]>