Removed content-replace from ICE-UDP examples per XEP-0176.
Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the initiator sends a content-replace action to the responder.
-The responder then acknowledges the content-replace action and sends a session-accept action.
-Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the responder sends a session-accept action to the initiator.
Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the initiator sends a content-replace action to the responder.
-The responder then acknowledges the content-replace action and sends a session-accept action.
-Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the responder sends a session-accept action to the initiator.
In this scenario, Romeo initiates a voice chat with Juliet using a transport method of ICE-UDP and an unencrypted profile of "RTP/AVP", but Juliet wants to chat securely so she requests the use of a secure transport as specified in &sdpdtls; (via a profile of "UDP/TLS/RTP/SAVP").
+In this scenario, Romeo initiates a voice chat with Juliet using a secure transport as specified in &sdpdtls; (via a profile of "UDP/TLS/RTP/SAVP").
The session flow is as follows:
|
- | content-replace |
- |<----------------------------|
- | ack |
- |---------------------------->|
- | content-accept |
- |---------------------------->|
- | ack |
- |<----------------------------|
| transport-info (X times) |
| (with acks) |
|<--------------------------->|
| STUN connectivity checks |
|<--------------------------->|
- | content-replace |
- |---------------------------->|
- | ack |
- |<----------------------------|
| session-accept |
|<----------------------------|
| ack |
@@ -1219,7 +1123,7 @@ Romeo Juliet
initiator='romeo@montague.lit/orchard'
sid='a73sjjvkla37jfea'>
-
+
@@ -1256,95 +1160,7 @@ Romeo Juliet
to='juliet@capulet.lit/balcony'
type='result'/>
]]>
- However, Juliet wants to make sure that the communications are encrypted, so she sends a content-replace action to Romeo.
-
-
-
-
-
-
-
-
- ]]>
- Romeo then acknowledges the content-replace action and, if it is acceptable, returns a content-accept action:
-
- ]]>
-
-
-
-
-
-
-
-
- ]]>
- The other party then acknowledges the acceptance.
-
- ]]>
- Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the initiator sends a content-replace action to the responder.
-
-
-
-
- [ ... ]
-
-
-
-
-
-
-
- ]]>
- The responder then acknowledges the content-replace action and sends a session-accept action.
-
- ]]>
+ Because the parties have chosen the Jingle ICE-UDP Transport Method, the initiator and responder exchange an open-ended number of possible candidate transports, perform connectivity checks, and agree upon a candidate transport as explained in XEP-0176. Once ICE negotiation is completed, the responder sends a session-accept action to the initiator.