On 30.03.20 09:24, Daniel-Constantin Mierla wrote:
On 30.03.20 07:09, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Have you tested with tcp/tls or with udp? There was a group of commits trying to propagate the tcp connection id as much as possible to speed up connection search, maybe that needs to be reset -- I can look into it, if you tested for tcp/tls.
This is what has no effect in branch route:
Mar 29 10:19:28 char /usr/bin/sip-proxy[26162]: INFO: ********* du = sip:127.0.0.1:5090;transport=tcp
Does this happen after a usrloc location lookup? Trying to figure out what destination-related processing is done before to see what fields were set...
I pushed two commits on master and branch 5.3 to skip reusing tcp connection id. See if it solves your case.
Cheers, Daniel