On Thu, Jul 12, 2012 at 1:33 AM, Peter Dunkley
wrote:
> Hi,
>
> I have just built Kamailio from Git master, configured TCP and TLS, and an
> HTTP event route. I was able to connect to Kamailio over TLS using Google
> Chrome (and saw the "SSL Error: The site's security certificate is not
> trusted
Hi,
I have just built Kamailio from Git master, configured TCP and TLS, and an
HTTP event route. I was able to connect to Kamailio over TLS using Google
Chrome (and saw the "SSL Error: The site's security certificate is not
trusted!" page). After I clicked on "Proceed anyway" I saw the log
messa
On Wed, Jul 11, 2012 at 9:37 PM, Peter Dunkley
wrote:
>
> Hi,
>
> WebSockets over TLS works which requires establishing a TLS connection and
> exchanging an HTTP request and response. It doesn't sound like this
> connection is even getting passed the TLS handshake part?
>
> Peter
>
Hi,
That was
Hi,
WebSockets over TLS works which requires establishing a TLS connection
and exchanging an HTTP request and response. It doesn't sound like this
connection is even getting passed the TLS handshake part?
Peter
On Wed, 2012-07-11 at 17:14 +0200, Klaus Darilion wrote:
> Maybe there were some ch
Maybe there were some changes fore websocket support which cause
problems. Do plain TCP connections work?
klaus
On 11.07.2012 16:20, Aft nix wrote:
On Wed, Jul 11, 2012 at 6:56 PM, Klaus Darilion
wrote:
I just tested TLS with Kamailio 3.3.0 and Eyebeam and it works. Make sure to
specify "ca_
On Wed, Jul 11, 2012 at 6:25 PM, Klaus Darilion
wrote:
> Does it work with your web browser?
>
> https://ip.address.ofyour.proxy:5061/
>
> At least the TLS handshake should work.
>
Yes i've tested that way. It shows server not found. I think the
problem is not related to
tls. The TCP connection i
On Wed, Jul 11, 2012 at 6:56 PM, Klaus Darilion
wrote:
> I just tested TLS with Kamailio 3.3.0 and Eyebeam and it works. Make sure to
> specify "ca_list" if intermediate certificates are used.
>
I was working with master branch, not 3.3 branch.
>
> regards
> Klaus
>
> On 09.07.2012 13:27, Aft ni
I just tested TLS with Kamailio 3.3.0 and Eyebeam and it works. Make
sure to specify "ca_list" if intermediate certificates are used.
regards
Klaus
On 09.07.2012 13:27, Aft nix wrote:
Hi,
I have enabled tls parameters as follows:
in kamailio.cfg
listen = tls::
in tls.cfg
[server::]
method
Does it work with your web browser?
https://ip.address.ofyour.proxy:5061/
At least the TLS handshake should work.
If you add the following snippet to your config you should also see the
response in your browser:
event_route[xhttp:request] {
xhttp_reply("200", "OK", "text/html","OK -
On Mon, Jul 9, 2012 at 10:24 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> also, can you provide more details about the case? Is it with the very first
> connection or you do some load testing and at some point you get this issue?
>
No, its not a part of load testing. it happens on the first c
On Mon, Jul 9, 2012 at 7:04 PM, Klaus Darilion
wrote:
> Use wireshark to analyze the TLS handshake
>
Thanks for the suggestion. I'll analyze it and post my findings.
> regards
> klaus
>
>
> On 09.07.2012 13:27, Aft nix wrote:
>>
>> Hi,
>>
>> I have enabled tls parameters as follows:
>>
>> in kam
Hello,
also, can you provide more details about the case? Is it with the very
first connection or you do some load testing and at some point you get
this issue?
Can you reproduce it always? Do you set different number of workers per
socket? What is the output of 'kamctl ps'?
Have you tried
Use wireshark to analyze the TLS handshake
regards
klaus
On 09.07.2012 13:27, Aft nix wrote:
Hi,
I have enabled tls parameters as follows:
in kamailio.cfg
listen = tls::
in tls.cfg
[server::]
method = TLSv1
verify_certificate = no
require_certificate = no
private_key = /usr/local/etc/kamai
Hi,
I have enabled tls parameters as follows:
in kamailio.cfg
listen = tls::
in tls.cfg
[server::]
method = TLSv1
verify_certificate = no
require_certificate = no
private_key = /usr/local/etc/kamailio/kamailio-selfsigned.key
certificate = /usr/local/etc/kamailio/kamailio-selfsigned.pem
Now if
14 matches
Mail list logo
