Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix transport parameter in load balancer Route #342
If a TLS target has to be contacted, but load balancer is set to terminate TLS, the server will send the request via TCP, even though the Request-URI contains ;transport=tls. In this case, JainSipUtils.findTransport will report "tls" transport, but that is not what should be used in the Route header if a connector with a different transport is used. The Route's transport and port should match the listening point of the load balancer, which will be TCP in this case.