Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(28)

Side by Side Diff: chrome/test/data/webrtc/manual/peerconnection-help.html

Issue 11618019: Update peerconnection-help.html to include instructions for creating a data channel. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 8 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> 1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
2 <html> 2 <html>
3 <head> 3 <head>
4 <title>WebRTC PeerConnection Manual Test Help Page</title> 4 <title>WebRTC PeerConnection Manual Test Help Page</title>
5 <link rel="StyleSheet" type="text/css" href="stylesheet.css"> 5 <link rel="StyleSheet" type="text/css" href="stylesheet.css">
6 <meta charset="utf-8"> 6 <meta charset="utf-8">
7 </head> 7 </head>
8 <body> 8 <body>
9 9
10 <h1>WebRTC PeerConnection Manual Test Help Page</h1> 10 <h1>WebRTC PeerConnection Manual Test Help Page</h1>
11 <p> 11 <p>
12 The test page is intended for testing WebRTC calls. 12 The test page is intended for testing WebRTC calls.
13 13
14 This is how you set up a normal call: 14 This is how you set up a normal call:
15 </p> 15 </p>
16 <ol> 16 <ol>
17 <li>Open this page in two tabs.</li> 17 <li>Open this page in two tabs.</li>
18 <li>Start the peerconnection server. Click on the question mark next 18 <li>Start the peerconnection server. Click on the question mark next
19 to the 'server' field for instruction on how to do that. The easiest 19 to the 'server' field for instruction on how to do that. The easiest
20 thing is to start it on localhost, but you can start it on any 20 thing is to start it on localhost, but you can start it on any
21 machine you like and connect to hostname:8888.</li> 21 machine you like and connect to hostname:8888.</li>
22 <li>Click the Connect button in both tabs.</li> 22 <li>Click the Connect button in both tabs.</li>
23 <li>Click the Call:Negotiate button in one of the tabs. You should see a bunch 23 <li>Click the Call:Negotiate button in one of the tabs. You should see a bunch
24 of printouts when this happens. Note that no streams are sent to 24 of printouts when this happens. Note that no streams are sent to
25 begin with (although you could run steps 5-6 before this step to get streams 25 begin with (although you could run steps 5-6 before this step to get streams
26 even in the initial call).</li> 26 even in the initial call).</li>
27 <li>Grant media access using the checkboxes and Request button.</li> 27 <li>Grant media access using the checkboxes and Request button.</li>
28 <li>Add the local stream by clicking the "Add" button, in both tabs.</li> 28 <li>Add the local stream by clicking the "Add" button, in both tabs.</li>
tnakamura 2012/12/19 14:49:30 nit - whitespace at the end of the line.
perkj_chrome 2012/12/20 08:56:23 Done.
29 <li>Now you must re-negotiate the call by clicking on Negotiate again.</li> 29 <li>Now you must re-negotiate the call by clicking on Negotiate again.</li>
30 <li>You should now have a call up and both sides should be receiving 30 <li>You should now have a call up and both sides should be receiving
31 media data (depending on what access you granted on the respective 31 media data (depending on what access you granted on the respective
32 pages).</li> 32 pages).</li>
33 <li>You can now choose to stop, re-request, re-send or disable streams 33 <li>You can now choose to stop, re-request, re-send or disable streams
34 in any way you like, or hang up and re-start the call. You don't 34 in any way you like, or hang up and re-start the call. You don't
35 need to disconnect: that's done automatically when you close the 35 need to disconnect: that's done automatically when you close the
36 page. Hanging up is NOT done automatically though.</li> 36 page. Hanging up is NOT done automatically though.</li>
37 </ol> 37 </ol>
38
39 <p>
40 To create a data channel:
41 </p>
42 <ol>
43 <li>Make sure Chrome is started with the --enable-data-channels flag.</li>
44 <li>Follow the instructions above to connect two tabs to a
45 peerconnection_server.</li>
tnakamura 2012/12/19 14:49:30 https://code.google.com/p/webrtc/issues/detail?id=
perkj_chrome 2012/12/20 08:56:23 The constrataint is hardcodec into jsep01_call.js
46 <li>Click the Data channel: Create button in one tab. Notice the status
47 changes to "connecting".</li>
48 <li>Click the Call:Negotiate button. You should see the status change to
49 "open" in both tabs. </li>
50 <li>Enter text in the textbox next to the Send data button and then click Send
51 data. Notice the text is received in the remote tab in the Received on data
52 channel text box. Data can be sent in both direct.</li>
53 <li>To close the channel press the Close button followed by Negotiate. Notice
54 the status change to "closed"</li>
55 </ol>
56
38 <p>Detailed descriptions:</p> 57 <p>Detailed descriptions:</p>
39 <ul> 58 <ul>
40 <li>Connect - once a connection is established, you generally won't 59 <li>Connect - once a connection is established, you generally won't
41 need to click this button again. Connecting really isn't something 60 need to click this button again. Connecting really isn't something
42 related to WebRTC as such, it's just the signalling solution.</li> 61 related to WebRTC as such, it's just the signalling solution.</li>
43 <li>Note that if more than two users/machines have established a 62 <li>Note that if more than two users/machines have established a
44 connection to the same PC server, you will get an error when 63 connection to the same PC server, you will get an error when
45 pressing this button. The test is hard-coded to only allow 2 peers 64 pressing this button. The test is hard-coded to only allow 2 peers
46 on the server at the same time.</li> 65 on the server at the same time.</li>
47 <li>Pressing the Add button for local streams will in effect add 66 <li>Pressing the Add button for local streams will in effect add
(...skipping 25 matching lines...) Expand all
73 [experimental]</li> 92 [experimental]</li>
74 <li>The Force Opus checkbox will remove all codecs except OPUS for all 93 <li>The Force Opus checkbox will remove all codecs except OPUS for all
75 outgoing messages sent by this page. Note that this ONLY means that 94 outgoing messages sent by this page. Note that this ONLY means that
76 we are guaranteed to send Opus to the other side; it does NOT mean 95 we are guaranteed to send Opus to the other side; it does NOT mean
77 that the other side will necessarily send Opus to us. To do that, 96 that the other side will necessarily send Opus to us. To do that,
78 you need to check the box on the other side too. You can either 97 you need to check the box on the other side too. You can either
79 check the box before the call, or check the box and then re-send the 98 check the box before the call, or check the box and then re-send the
80 local stream.</li> 99 local stream.</li>
81 </ul> 100 </ul>
82 101
102
103
83 </body> 104 </body>
84 </html> 105 </html>
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698