When packet arrives at from the WebSocket its length usually more that 1500 bytes
THat is the problem. sometimes sdp data lost while sending. If asterisk at the sama machine it uses lo interface and then it is not a problem but for remote servers it can be.

I didnt thought about keepalive. I suppose it can help.

2016-09-08 15:04 GMT+03:00 Daniel Tryba <d.tryba@pocos.nl>:
On Thu, Sep 08, 2016 at 02:43:03PM +0300, Yuriy Gorlichenko wrote:
> yes. Thats will be great because in some system design it must use same
> port that listening for sendinf like in UDP for example for transcoding SIP
> overĀ  WebSocket to SIP over TCP and masking registration behind thanscoder.
>
> Like User sends registration, kamailio just Transcoding this request to TCP
> and then resend this registration packet to Asterisk.
> With this example asteisk must originate all PACKETS to TCP port of
> kamailio but it tries to send it to port from wich request arrived and if
> use TCP it will not equal port that kamailio listening for TCP.

And this is a problem? Since all requests from kamailio to that asterisk
should be send over the same connection it will stay open for some time,
and enabling qualify for the users on asterisk will keep is open.

But I'd communicate over UDP with asterisk/any backend anyway, so what
is the reason for TCP?

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users