Hello,
I have 2 clients. 1 using websocket and 1 mobile using TLS.
Both can call each other perfectly. After 24-48 hours calls from mobile to
websocket failed with an error message: TCP/TLS connection (id: 0) for
WebSocket could not be found.
At the same time I can make calls from the websocket cl
That's quite strange, the registrar/usrloc are not related to websocket
in storing the connection id, they see it as a tcp/tls connection. I
checked on a test server and all tcp/tls contacts have connection id and
socket field set.
Do you get any error messages when processing the REGISTER?
If no
Here is what one of my registrations look like
id: 148
ruid: uloc-5e999161-1782-1
username: 2000
domain: ws-test.com
contact: sips:2000@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss
received: sip:98.209.240.245:63356;transport=ws
path:
Hello,
I upgrade to 5.3 and got the same result. But, I noticed that changing the
connection_id in the database to the connection_id of the web socket
connection listed by ws.dump made it work.
So, it looks like the socket or the connection_id is not being set when the
record is stored by us
Hello,
did you print the log message just before t_relay()?
Can you also print the tcp and tls connections via rpc? I am not sure if
the websocket keeps a separate list of connections, but tcp/tls should
have the lists used for routing.
It would be better to upgrade to 5.3, because 5.1 is out of
Hey Daniel,
It returns:
[LOCATION] ru: sips:2000@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss,
nh(u): sip:98.209.240.245:50453;transport=ws
This matches the output from
kamcmd ws.dump
connections: {
29: wss:98.209.240.245:50453 -> wss:134.122.27.49:4443 (st
Hello,
when id is 0, then the search of the connection is done by target
address. For some reason, the destination is not matching the
connection. Try to print $nh(u) before relaying to see where it is
supposed to be sent.
Cheers,
Daniel
On 15.04.20 16:54, Mack Hendricks wrote:
> Hello,
>
> I’m
Hello,
I’m running kamailio 5.1.10 (x86_64/linux)
The connection_id in usrloc is -1 for some reason so the id doesn’t match for
sure. But, I thought that it would match on the received address of the WS
client because the output from ws.dump shows that the connection address and
port matches
Hello,
what version of Kamailio do you use?
That message is printed when the connection is not found by id or by
destination address.
Cheers,
Daniel
On 15.04.20 07:11, Mack Hendricks wrote:
> Hey All,
>
>
>
> I get this message when trying to route request to a WebSocket client:
>
>
> Apr 15 04
Hey All,
I get this message when trying to route request to a WebSocket client:
Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]: DEBUG:
[core/msg_translator.c:1762]: check_boundaries(): no multi-part body
Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]: DEBUG:
[
10 matches
Mail list logo
