[asterisk-users] WSS over Asterisk
steveng.1988 at gmail.com
Wed Jun 11 20:21:25 CDT 2014
I am using Asterisk v12.3.
temporarily fix for SIPML5 to Asterisk:
WS works for me, its just wss which I'm stuck currently.
On Thu, Jun 12, 2014 at 4:37 AM, Miguel Molina <
mfmolina-listas at millenium.com.co> wrote:
> El 11/06/2014 1:52 p. m., Matthew Jordan escribió:
> On Wed, Jun 11, 2014 at 1:32 PM, William Hetherington <will at willwh.com>
>> 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
>> 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
> It is broken in Chrome (firefox never had SDES) because the WebRTC
> standard favoured the DTLS SRTP implementation instead of the SDES one. The
> thing is that although Asterisk supports DTLS implementation, it only
> supports SHA-1 hashing but both Firefox and Chrome work with SHA-256. The
> patch proposed in ASTERISK-22961 is an effort to solve this issue.
> Best regards
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-users