[sr-dev] [kamailio/kamailio] tcp_reuse_port: ACK cannot be delievered to WebRTC client (#2849)

sergey-safarov notifications at github.com
Sat Sep 11 13:40:16 CEST 2021

yes @arsperger, you are correct. here is the wrong Route header used in `ACK` message.
Wrong route header used because of Kamailio inserter wrong `Record-Route` header.

WebRTC client really connected to the socket `tls:` but Record-Route header generated like
INVITE sips:safarov at df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss SIP/2.0
Record-Route: <sips:;transport=ws;r2=on;lr=on;ftag=j4aU17p3BvH0e;did=698.6e42>
Record-Route: <sips:[2600:1f18:578:5701::7e];transport=tcp;r2=on;lr=on;ftag=j4aU17p3BvH0e;did=698.6e42>
Record-Route: <sip:[2600:1f14:6d8:5408::100]:5080;transport=tcp;r2=on;lr=on;ftag=j4aU17p3BvH0e>
Record-Route: <sip:[2600:1f14:6d8:5408::100];transport=tcp;r2=on;lr=on;ftag=j4aU17p3BvH0e>
Via: SIP/2.0/WSS;branch=z9hG4bKa53e.f43ae42f2fefe414dabc1a6739b19bbe.0;i=3
Here is top `Record-Route` should contain port "7001" but really is not.

I was replaced use of `record_route` by
record_route_preset(";transport=ws;r2=on", "[2600:1f18:578:5701::7e];transport=tcp;r2=on");
This alow me to specify which sockets need to use for call dialog and now ACK properly delivered to WebRTC client.

The issue about missed port in `Record-Route` header will be created.
This ticket is resolved.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20210911/b30fe229/attachment.htm>

More information about the sr-dev mailing list