You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Connect to bridge using conf-call.org using DTLS-SRTP via Chrome.
2. Observe chrome://webrtc-internals and see that process stalls on
iceGatheringStateChange: Checking
3. Sniff with WireShark, and filter for DTLS type packets, and observe.
- Telepresence->Client: Client Hello
- Client->Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
- Client->Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
- Client->Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
- Client->Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
- Client->Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
(Repeated with no response)
What is the expected output? What do you see instead?
When the DTLS/SRTP connection succeeds I see instead:
- Telepresence -> Client: Client Hello
- Client -> Telepresence: Server Hello, Certificate, Server Key Exchange,
Certificate Request, Server Hello Done
- Telepresence -> Client: Certificate (Fragment), Certificate (Reassembled),
Client Key Exchange, Certificate Verify, Change Cipher Spec, Encrypted
Handshake Message
- Client -> Telepresence: Change Cipher Spec, Encrypted Handshake Message
What version of the product are you using? On what operating system?
Ubuntu Linux 12.04
Doubango 2.0.1089
https://telepresence.googlecode.com/svn/trunk@140
Please provide any additional information below.
I've attached the wireshark captures for both a good (Video established) and a
bad (Black video) session.
Original issue reported on code.google.com by [email protected] on 10 Jul 2014 at 9:04
Original issue reported on code.google.com by
[email protected]
on 10 Jul 2014 at 9:04Attachments:
The text was updated successfully, but these errors were encountered: