Daniel-Constantin Mierla writes:
> > Are you sure you are using WSS with that config or just WS?
> > The problem is I cant debug since I have no errors in regular log :(
> > just seems a handshake issue
> One thing I also noticed lately, if I am on https page and try to make a
> ws (tcp) connec
On 11/09/14 16:53, Manuel Camarg wrote:
Daniel, websocket is not "downgradeable" under https, that's why I'm
trying to make this work
As I said in the first message here is the error log in the browser:
In the Chrome console:
/*__tsip_transport_ws_onerror
*/
/*__tsip_transport_ws_onclose
*/
Hello,
On 10/09/14 23:15, Manuel Camarg wrote:
Hello Juha
They why you think i'm encountering this issue based on the beginning
of this topic?
http://lists.sip-router.org/pipermail/sr-users/2014-September/084699.html
Daniel:
> However, more recent versions of browsers don't work with that an
Daniel, websocket is not "downgradeable" under https, that's why I'm trying
to make this work
As I said in the first message here is the error log in the browser:
In the Chrome console:
*__tsip_transport_ws_onerror *
*__tsip_transport_ws_onclose *
Regards,
Manuel
*Manuel Camargo*
Teléfono: 6
On 11/09/14 16:30, Manuel Camarg wrote:
I used jssip during testing. It doesn't differ much from sipml5 from
regular operations, but it does not work with wss (at least with my
current config, the mentioned before)
Are you sure you are using WSS with that config or just WS?
The problem is I c
I used jssip during testing. It doesn't differ much from sipml5 from
regular operations, but it does not work with wss (at least with my current
config, the mentioned before)
Are you sure you are using WSS with that config or just WS?
The problem is I cant debug since I have no errors in regular l
On 10/09/14 19:05, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
On the other hand, I remember that I tested with default example some
time ago and worked. However, more recent versions of browsers don't
work with that anymore. What browser (or wss client) are you using?
i have used j
Users] TLS Handshake failing with WSS
On 10/09/14 18:43, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The set_reply_close() should be removed from there.
> why is that? my wss clients
are they ws (over tcp) or wss (over tls)?
> work fine even when i
Manuel Camarg writes:
> They why you think i'm encountering this issue based on the beginning of
> this topic?
> http://lists.sip-router.org/pipermail/sr-users/2014-September/084699.html
perhaps it has something to do with sipml5. i'm using jssip based ws
client. try with the jssip demo client to
Hello Juha
They why you think i'm encountering this issue based on the beginning of
this topic?
http://lists.sip-router.org/pipermail/sr-users/2014-September/084699.html
Daniel:
> However, more recent versions of browsers don't work with that anymore
Do you have an example of some functional wss
Daniel-Constantin Mierla writes:
> On the other hand, I remember that I tested with default example some
> time ago and worked. However, more recent versions of browsers don't
> work with that anymore. What browser (or wss client) are you using?
i have used jsip based web client both with firef
On 10/09/14 18:43, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The set_reply_close() should be removed from there.
why is that? my wss clients
are they ws (over tcp) or wss (over tls)?
work fine even when i have:
event_route[xhttp:request] { # Handle HTTP requests
se
Daniel-Constantin Mierla writes:
> The set_reply_close() should be removed from there.
why is that? my wss clients work fine even when i have:
event_route[xhttp:request] { # Handle HTTP requests
set_reply_close();
set_reply_no_connect();
this was included in the original instr
The set_reply_close() should be removed from there.
For digest authentication, simply use the same functions as for sip
(e.g., from auth/auth_db modules).
Cheers,
Daniel
On 09/09/14 16:49, Manuel Camarg wrote:
According to this article I mentioned in the beginning:
http://nil.uniza.sk/sip/k
According to this article I mentioned in the beginning:
http://nil.uniza.sk/sip/kamailio/configuring-kamailio-4x-websocket
In http:request they do straight away the set_reply_close();
I don't know exactly if this kamailio.cfg implementation may be useful for
working with WSS:
event_route[xhttp:
Hello,
from the logs you sent now, it appears that you have set_reply_close()
in config, therefore the connection is closed after sending the reply.
Cheers,
Daniel
On 08/09/14 20:10, Manuel Camarg wrote:
Hello Daniel:
Trying it, accessing via Browser here is the log, similarities with
the
Hello Daniel:
Trying it, accessing via Browser here is the log, similarities with the
access via SIPML5, no errors, no warnings (at least as far as I can see):
DEBUG: [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp
connection: 123.123.123.123
DEBUG: [tcp_main.c:1096]: tcpconn_new(): tcpcon
Hello,
if you run latest versions of web browsers, they become more restrictive
on wss connection. Be sure that the cetificate is also trusted by the
web browser.
You can go with the web browser to https://ipofkamailio:portforwss and
see if you get any warnings there.
Cheers,
Daniel
On 06
I'm trying to implement WSS with Kamailio
Thing is that WS works fine, I've followed:
http://nil.uniza.sk/sip/kamailio/configuring-kamailio-4x-websocket
modparam("tls", "config", "webrtc/tls.cfg")
In a tls.cfg file I have :
[server:default]
method = SSLv23
verify_certificate = no
require_certific
19 matches
Mail list logo
