Web resources are usually build on request/response paradigm such as HTTP , SIP messages . This means that server responds only when a client requests it to. This made web intercations very slow and unsuited for VOIP signalling
Long Poll involved repeated polling checks to load new server resources by itself instead of client made explicit request
AJAX and multipart XHR tried to patch the problem by selective reloading however they still required that client perform the mapping for an incomig reply to map to correct request.
However due to overhead latency involved with HTTP transaction and its working mode to open new TCP connetion for every request and reponse and add HTTP headers, none of them were suited to realtime operations
Websocket is the current (2017) most idelistic solution to perform realtime sigalling suited to VOIP requirnments due to its nature os establish a socket .
Websocket Protocol
Enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code.
protocol consists of an opening handshake followed by basic message framing, layered over TCP.
handshake is interpreted by HTTP servers as an Upgrade request.
Secure websocket example :
Request URL: wss://site.com:8084/socket.io/?transport=websocket&sid=hh3Dib_aBWgqyO1IAAEL
Request Method: GET
Status Code: 101 Switching Protocols
Response Headers
Connection: Upgrade
Sec-WebSocket-Accept: UVhTdFOWfywGyQTKDRZyGuhkfls=
Sec-WebSocket-Extensions: permessage-deflate
Upgrade: websocket
Request Headers
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Cache-Control: no-cache
Connection: Upgrade
Host: site.com:8085
Origin: https://site.com:8084
Pragma: no-cache
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Sec-WebSocket-Key: 06FNaHge8GLGVuPFxV2fAQ==
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36
Query String parameters
transport: websocket
sid: hh3Dib_aBWgqyO1IAAEL
Working with websockets
A new websocket can be opned with ws or wss and it can have sub protocols like in example .
var wsconnection = new WebSocket('wss://voipsever.com', ['soap', 'xmpp']);
It can be attached with event handlers
wsconnection.onopen = function () {
...
};
wsconnection.onerror = function (error) {
console.log('WebSocket Error ' + error);
};
wsconnection.onmessage = function (e) {
console.log('message received : ' + e.data);
};
Send Data on websocket
message string
wsconnection.send('Hi);
Blob or ArrayBuffer object to send binary data
Ex : Sending canvas ImageData as ArrayBuffer
var img = canvas_context.getImageData(0, 0, 400, 320);
var binary = new Uint8Array(img.data.length);
for (var i = 0; i < img.data.length; i++) {
binary[i] = img.data[i];
}
wsconnection.send(binary.buffer);
Ex : sending file as Blob
var file = document.querySelector('input[type="file"]').files[0];
wsconnection.send(file);
Closing the connection
if (socket.readyState === WebSocket.OPEN) {
socket.close();
}
Registry for Close codes for WS
1000 Normal Closure [IESG_HYBI] [RFC6455]
1001 Going Away [IESG_HYBI] [RFC6455]
1002 Protocol error [IESG_HYBI] [RFC6455]
1003 Unsupported Data [IESG_HYBI] [RFC6455]
1004 Reserved [IESG_HYBI] [RFC6455]
1005 No Status Rcvd [IESG_HYBI] [RFC6455]
1006 Abnormal Closure [IESG_HYBI] [RFC6455]
1007 Invalid frame payload data [IESG_HYBI] [RFC6455]
1008 Policy Violation [IESG_HYBI] [RFC6455]
1009 Message Too Big [IESG_HYBI] [RFC6455]
1010 Mandatory Ext. [IESG_HYBI] [RFC6455]
1011 Internal Error [IESG_HYBI] [RFC6455][RFC Errata 3227]
1012 Service Restart [Alexey_Melnikov] [http://www.ietf.org/mail-archive/web/hybi/current/msg09670.html]
1013 Try Again Later [Alexey_Melnikov] [http://www.ietf.org/mail-archive/web/hybi/current/msg09670.html]
1014 The server was acting as a gateway or proxy and received an invalid response from the upstream server. This is similar to 502 HTTP Status Code. [Alexey_Melnikov] [https://www.ietf.org/mail-archive/web/hybi/current/msg10748.html]
1015 TLS handshake [IESG_HYBI] [RFC6455]
1016-3999 Unassigned
4000-4999 Reserved for Private Use [RFC6455]
WebSocket Subprotocol Name Registry
- MBWS.huawei.com MBWS
- MBLWS.huawei.com MBLWS
- soap soap
- wamp WAMP (“The WebSocket Application Messaging Protocol”)
- v10.stomp Name: STOMP 1.0 specification
- v11.stomp Name: STOMP 1.1 specification
- v12.stomp Name: STOMP 1.2 specification
- ocpp1.2 OCPP 1.2 open charge alliance
- ocpp1.5 OCPP 1.5 open charge alliance
- ocpp1.6 OCPP 1.6 open charge alliance
- ocpp2.0 OCPP 2.0 open charge alliance
- ocpp2.0.1 OCPP 2.0.1
- rfb RFB [RFC6143]
- sip WebSocket Transport for SIP (Session Initiation Protocol) [RFC7118]
- notificationchannel-netapi-rest.openmobilealliance.org OMA RESTful Network API for Notification Channel
- wpcp Web Process Control Protocol (WPCP)
- amqp Advanced Message Queuing Protocol (AMQP) 1.0+
- mqtt mqtt [MQTT Version 5.0]
- jsflow jsFlow pubsub/queue protocol
- rwpcp Reverse Web Process Control Protocol (RWPCP)
- xmpp WebSocket Transport for the Extensible Messaging and Presence Protocol (XMPP) [RFC7395]
- ship SHIP – Smart Home IP SHIP (Smart Home IP) is a an IP based approach to plug and play home automation and smart energy / energy efficiency, which can easily be extended to additional domains such as Ambient Assisted Living (AAL). SHIP can be used solely on the customer premises or can be integrated into a cloud based solution.
- mielecloudconnect Miele Cloud Connect Protocol This protocol is used to securely connect household or professional appliances to an internet service portal via a public communication network in order to enable remote services.
- v10.pcp.sap.com Push Channel Protocol
- msrp WebSocket Transport for MSRP (Message Session Relay Protocol) [RFC7977]
- v1.saltyrtc.org
- TLCP-2.0.0.lightstreamer.com TLCP (Text Lightstreamer Client Protocol)
- bfcp WebSocket Transport for BFCP (Binary Floor Control Protocol)
- sldp.softvelum.com Softvelum Low Delay Protocol SLDP is a low latency live streaming protocol for delivering media from servers to MSE-based browsers and WebSocket-enabled applications.
- opcua+uacp OPC UA Connection Protocol
- opcua+uajson OPC UA JSON Encoding
- v1.swindon-lattice+json Swindon Web Server Protocol (JSON encoding)
- v1.usp USP (Broadband Forum User Services Platform)
- mles-websocket mles-websocket
- coap Constrained Application Protocol (CoAP) [RFC8323]
- TLCP-2.1.0.lightstreamer.com TLCP (Text Lightstreamer Client Protocol)
- sqlnet.oracle.com sqlnet This protocol is used for communication between Oracle database client and database server, and its usage as subprotocol of websocket is primarly geared towards cloud deployments. sqlnet supports bi-directional data transfer and is full duplex in nature.
- oneM2M.R2.0.json oneM2M R2.0 JSON
- oneM2M.R2.0.xml oneM2M R2.0 XML
- oneM2M.R2.0.cbor oneM2M R2.0 CBOR
- transit Transit
- 2016.serverpush.dash.mpeg.org MPEG-DASH-ServerPush-23009-6-2017
- 2018.mmt.mpeg.org MPEG-MMT-23008-1-2018
- CLUE CLUE
- webrtc.softvelum.com Softvelum WebSocket signaling protocol WebRTC live streaming requires WebSocket-based signaling protocol for every specific implementation. Softvelum products will use this subprotocol for signaling
websocket libraries
C++: libwebsockets
Erlang: Shirasu.ws
Java: Jetty
Node.JS: ws
Ruby:
em-websocket
EventMachine
Faye
Python:
Tornado,
pywebsocket
PHP: Ratchet, phpws
Javascript:
Socket.io
ws
WebSocket-Node
GoLang:
Gorilla
C#:
Fleck
Ref :
RFC 6455 – The websocket protocol
Websocket Protocol Registeries : http://www.iana.org/assignments/websocket/websocket.xml
https://www.html5rocks.com/en/tutorials/websockets/basics/
IANA websocket -https://www.iana.org/assignments/websocket/websocket.xhtml
Telecom R & D 