Closed WolandPL closed 7 years ago
Should be working @WolandPL. Jain SIP stack that runs underneath supports it and I tested it a couple of months back; just uncomment wss instead of tls ;)
I did uncomment wss and I get WSS in VIA header and "transport" in CONTACT header, but server still seems not to recognize it as a websocket traffic. Are you sure setting transport to WSS is enough to really send REGISTER to WebSocket? I tried adding "wss://" at the beginning of Signaling Domain but then it fails valdiation (and I saw exactly that - wss://... as a registrar in your javascript library. Maybe that's the problem?
@WolandPL just tried again with WSS and it is working fine. You must not add wss:// in the beginning of signaling domain. For example in my case domain is:
cloud.restcomm.com:5063
Notice that I had to explicitly use port 5063 in our case since the WSS port is 5063. If with these changes you still get issues, please share more information like android logcat
Is there a way to use WebSocket as transport? In jainSipClientBind method in org.restcomm.android.sdk.SignalingClient.JainSipClient I can see:
looking like you tried or plan to implement WebSockets, but currently it's not available. Is this right?