New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix transport parameter in load balancer Route #342

Merged
merged 1 commit into from Sep 14, 2017

Conversation

Projects
None yet
2 participants
@gyoetam
Contributor

gyoetam commented Sep 14, 2017

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.

Fix transport parameter in load balancer Route
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.

@xhoaluu xhoaluu merged commit d0fda56 into RestComm:master Sep 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment