athibanraj / telepresence

Automatically exported from code.google.com/p/telepresence
0 stars 0 forks source link

ssl key and too much latency #36

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. telepresence server is installed on LAN, follow the steps as shown in the 
section of 'Support_Testing_the_system'
2. telepresence needs ssl configuration, so I follow below steps to generate 
ssl certificates : 
https://groups.google.com/forum/#!topic/doubango/asAfP5ZCgdI
4. to extract public key from private key : openssl rsa -in key.ca.cg.pem 
-pubout > key.ca.cg.pub
5  I get ca, public key, and private key, which are crt.ca.cg.pem, 
key.ca.cg.pub, key.ca.cg.pem respectively

What is the expected output? What do you see instead?

webrtc client is expected to join the default bridge without error.

However, telepresence log show something wrong with ssl certificates. what's 
wrong with my method of key/ca generation. In addition, two much latency are 
reported. how to reduce transport latency via telepresence.cfg?

For details please reference attachment.

What version of the product are you using? On what operating system?
telepresence revision : 140
doubango revision : 1089
operating system : CentOS 64bit ver6.5

Please provide any additional information below.

telepresence/doubango config.log, wireshare file, and ssl ca/key are uploaded 
as attachment.

Original issue reported on code.google.com by andrewm...@gmail.com on 20 Jun 2014 at 7:23

Attachments: