Update peerconnection-help.html to include instructions for creating a data channel.

chrome/test/data/webrtc/manual/peerconnection-help.html

Index: chrome/test/data/webrtc/manual/peerconnection-help.html
diff --git a/chrome/test/data/webrtc/manual/peerconnection-help.html b/chrome/test/data/webrtc/manual/peerconnection-help.html
index 59c868e3fbbae31e41fe5f3c95e5b9e2cae149c7..eb1cfd9c02dee515a12f6900767750c38bf57c8d 100644
--- a/chrome/test/data/webrtc/manual/peerconnection-help.html
+++ b/chrome/test/data/webrtc/manual/peerconnection-help.html
@@ -25,7 +25,7 @@
     begin with (although you could run steps 5-6 before this step to get streams
     even in the initial call).</li>
   <li>Grant media access using the checkboxes and Request button.</li>
-  <li>Add the local stream by clicking the "Add" button, in both tabs.</li>
+  <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.

   <li>Now you must re-negotiate the call by clicking on Negotiate again.</li>
   <li>You should now have a call up and both sides should be receiving
     media data (depending on what access you granted on the respective
@@ -35,6 +35,25 @@
     need to disconnect: that's done automatically when you close the
     page. Hanging up is NOT done automatically though.</li>
 </ol>
+
+<p>
+  To create a data channel:
+</p>
+<ol>
+  <li>Make sure Chrome is started with the --enable-data-channels flag.</li>
+  <li>Follow the instructions above to connect two tabs to a
+   peerconnection_server.</li>

[tnakamura, 2012/12/19 14:49:30]

https://code.google.com/p/webrtc/issues/detail?id=876#c7 mentions the need for a
constraint when establishing the peerconnection if you want to use data
channels. I don't see any reference to a constraint in this new block of
instructions. Is a constraint no longer necessary in more recent versions of
Chrome?

[perkj_chrome, 2012/12/20 08:56:23]

The constrataint is hardcodec into jsep01_call.js and is not needed to be
inserted from the test page.
   peerConnection = new webkitRTCPeerConnection(
        servers, { optional:[ { RtpDataChannels: true } ]});

+  <li>Click the Data channel: Create button in one tab. Notice the status 
+  changes to "connecting".</li>
+  <li>Click the Call:Negotiate button. You should see the status change to 
+  "open" in both tabs. </li>     
+  <li>Enter text in the textbox next to the Send data button and then click Send
+   data. Notice the text is received in the remote tab in the Received on data 
+  channel text box. Data can be sent in both direct.</li>
+  <li>To close the channel press the Close button followed by Negotiate. Notice 
+  the status change to "closed"</li>
+</ol>
+
 <p>Detailed descriptions:</p>
 <ul>
   <li>Connect - once a connection is established, you generally won't
@@ -80,5 +99,7 @@
     local stream.</li>
 </ul>
 
+
+
 </body>
 </html>