16a04273bb
- Only showing text about browser needing WebRTC support if support not detected. Text is now contains more information and link to blog post. - Removed the debug buttons. - Clarifications and corrections in the readme file. Review URL: https://webrtc-codereview.appspot.com/352015 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1491 4adac7df-926f-26a2-2b94-8c16560cd09d
46 lines
2.0 KiB
Plaintext
46 lines
2.0 KiB
Plaintext
This test client is a simple functional test for a WebRTC enabled browser. It
|
|
has only been tested with Chrome, and is most likely only working with Chrome at
|
|
the moment. The following instructions are in part Chrome specific.
|
|
|
|
The following is necessary to run the test:
|
|
- A WebRTC enabled Chrome binary. (Available in dev or canary channel, 18.0.1008
|
|
or newer.)
|
|
- A peerconnection_server binary (make peerconnection_server).
|
|
|
|
It can be used in two scenarios:
|
|
1. Single client calling itself with the server test page
|
|
(peerconnection/samples/server/server_test.html) in loopback mode as a fake
|
|
client.
|
|
2. Call between two clients.
|
|
|
|
To start the test for scenario (1):
|
|
1. Start peerconnection_server.
|
|
2. Start the WebRTC Chrome build:
|
|
$ <path_to_chrome_binary>/chrome --enable-media-stream
|
|
The --enable-media-stream flag is required for the time being.
|
|
3. Open the server test page, ensure loopback is enabled, choose a name (for
|
|
example "loopback") and connect to the server.
|
|
4. Open the test page, connect to the server, select the loopback peer, click
|
|
call.
|
|
|
|
To start the test for scenario (2):
|
|
1. Start peerconnection_server.
|
|
2. Start the WebRTC Chrome build, see scenario (1).
|
|
3. Open the test page, connect to the server.
|
|
4. On another machine, start the WebRTC Chrome build.
|
|
5. Open the test page, connect to the server, select the other peer, click call.
|
|
|
|
Note 1: There is currently a limitation so that the camera device can only be
|
|
accessed once, even if in the same browser instance. Hence the need to use two
|
|
machines for scenario (2).
|
|
|
|
Note 2: The web page must normally be on a web server to be able to access the
|
|
camera for security reasons.
|
|
See http://blog.chromium.org/2008/12/security-in-depth-local-web-pages.html
|
|
for more details on this topic. This can be overridden with the flag
|
|
--allow-file-access-from-files, in which case running it over the file://
|
|
URI scheme works.
|
|
|
|
Note 3: It's possible to specify the server and name in the url:
|
|
.../webrtc.html?server=my_server&name=my_name
|