Installed ws and used a noServer WebSocketServer to handle upgrades on a single path of the existing Express HTTP server, with signature verification on the upgrade request. Also used the client side in the end-to-end harness to emulate the telephony provider.
- What worked
- The noServer mode made it simple to gate upgrades by path and custom auth before accepting the socket. Client and server worked without issues in the harness, including abrupt closes.