Disclaimer: This repository is a git-svn mirror of the project found at http://java.net/projects/jsip whose original repository is developed collaboratively by the Advanced Networking Technologies Division at the National Institute of Standards and Technology (NIST) - an agency of the United States Department of Commerce and by a community of individual and enterprise contributors. TeleStax, Inc. will perform some productization work, new features experimentation branches, etc for its TelScale jSIP product that doesn't concern the community from the main repository hence this git repository.
We are facing a problem where, scenario is the following:
client -> WSS -> proxy -> websocket->restcommLB -> tcpRestcomm
The issue is that the transport is changed at proxy from WSS to WS.
At the moment, we are just parsing the VIA header put from client to add IP:PORT.
What, it is necessary to patch as well the transport in case that is different from the one used at the VIA header.
We are facing a problem where, scenario is the following:
client -> WSS -> proxy -> websocket->restcommLB -> tcpRestcommThe issue is that the transport is changed at proxy from WSS to WS. At the moment, we are just parsing the VIA header put from client to add IP:PORT. What, it is necessary to patch as well the transport in case that is different from the one used at the VIA header.You can find a pcap here: https://s3.amazonaws.com/proxy-tranport-change/ws07.pcap