Thanks for the clarification. The latest posts were, respectively, "Firefox
currently treats the caller as the server and the callee as the client" (which
is what you just confirmed again, IIUC), and "I should mention that we reversed
this order about a month ago, which may have been confusing t
On Tue, Apr 30, 2013 at 8:40 AM, wrote:
> Hi Eric,
>
> apologies for this very late reply to a post you sent a couple of months
> ago, but I only recently started trying to get DTLS working in Asterisk as
> well. I'm still stuck with a few other issues, but I'd like to focus on
> this one at firs
Hi Eric,
apologies for this very late reply to a post you sent a couple of months ago,
but I only recently started trying to get DTLS working in Asterisk as well. I'm
still stuck with a few other issues, but I'd like to focus on this one at first
and then try and address the other ones in other
I should mention that we reversed this order about a month ago,
which may have been confusing to people. It was announced, but
maybe not as widely as one might have liked.
-Ekr
On Fri, Feb 22, 2013 at 8:06 AM, Eric Rescorla wrote:
> Firefox currently treats the caller as the server and the cal
Firefox currently treats the caller as the server and the callee as
the client. (This is the recommended configuration from 5763).
Eventually we will do RFC 4572 roles as defined in
RFC 5763/5764.
-Ekr
On Fri, Feb 22, 2013 at 5:17 AM, Mamadou Diop wrote:
> Hello,
>
> I'm using Nightly "22.0a1
Hello,
I'm using Nightly "22.0a1 (2013-02-20)" and making call from chrome to
FF through a gateway. The problem is that there is a role conflict in
DTLS. FF is the called party but is sends "Client Hello" message. Our
gateway uses rfc4145 to determine roles. If the remote party doesn't
support thi
6 matches
Mail list logo
