DTLS Bad Certificate error by Chrome on same tab during WebRTC call after gateway restart.

[Saurabh Srivastava]

Hi,

I am testing WebRTC calls on Chrome 34.0.1847.131 m on Windows 7.

Chrome gives a DTLS Bad Certificate (42) error during DTLS handshake on same browser tab after our gateway is restarted.

Here are the steps which reproduces problem at my end: 

1. I dial a call ( Chrome sends offer SDP and gateway replies back with an Answer SDP), STUN and DTLS handshake is good, RTP flows and media is seen on Chrome. 

2. Restart gateway.

3. Refresh same browser tab to recapture local media (mic and cam) and establish connection with gateway. Dial again. No media flows between endpoints. Wireshark traces tell DTLS Bad Certificate (42) error code by Chrome.

4. If a new call is dialled from a new Chrome tab, DTLS handshake is ok and media seen on new tab. Problem is also not observed after Chrome restart and making a new call.

5. Problem is not seen in Mozilla FF.

Has anybody seen this kind of behaviour on same Chrome tab earlier ?

I guess we might want to see what different/ initialization we do on a new Chrome tab regarding DTLS and certificates.

Could this be a possible Chrome issue ? Comments and suggestions are welcome.

Thanks,

Saurabh Srivastava

[Justin Uberti]

In the past this was caused by the remote side reusing a certificate serial number with different certs.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.