On Wed, Jun 11, 2014 at 1:32 PM, William Hetherington <w...@willwh.com> wrote:
> Chrome 35 broke all of this.... you need to be using DTLS now I believe. > > I had working secure web sockets with asterisk 12.2.x and chrome 34.... > and then google broke eveything :) > > I have not yet got around to test out DTLS etc. with chrome 35 > > Just so I don't waste too much time when I go to test, does anyone know if > all that's required for DTLS on the asterisk side is the following in > sip.conf? > > dtlsenable=yes > dtlsverify=yes > dtlsrekey=60 > dtlscafile=/usr/local/share/ca-certificates/myCA.crt > dtlscertfile=/etc/ssl/mycert.com.pem > dtlssetup=actpass > > I assume I also need TLS configs in http.conf > > Signalling is independent of the media; DTLS only affects the media. However, there are known issues with Chrome's negotiation of DTLS and Asterisk - see https://issues.asterisk.org/jira/browse/ASTERISK-22961 -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users