db2crush / webrtc-signaling-server

A nodejs-based webrtc signaling server built with web sockets. This follows the concept of real telephone calling and receiving. It is not a process to connect to any domain like apprtc.

Introduction

WebRTC-Signaling-Server

Contributor

@name SangGee Park (delbert)

@contact [email protected]

@region Seoul, South Korea

Description

nodejs, es6, websocket, JSON

Folder Structure

├── index.js
├── test
├── server
└── system
    ├── modules
    │   └── …
    ├── module.js (super module)
    ├── config.js (config module)
    └── system.js (top module)

Git Branch

├── master

Build and Run

1. Install all of denpendencies in the pacakage.json

 npm install

2. Simply enter the following command and the server opens with https://localhost:90 or http://localhost:90

development
npm run start

production
npm run build && npm run prod

dist

├── server   (server    module)
├── system   (signaling module)
├── index.js (intro     file)

Test

Unit tests are Mocha based. Load tests are artillery based.

Simply enter the following command and checkout log.

npm run server-test
npm run system-test
npm run signaling-test
npm run load-test

Version

0.0.1

webrtc-signaling-server's Issues

Problem with system-tests

Hey,
The tests practically don't work, can you look into it?

Problem

...
...
Wed, 17 Mar 2021 07:24:25 GMT uncaughtException:Unexpected server response: 301
Error: Unexpected server response: 301
    at ClientRequest.<anonymous> (/var/www/webrtc/signal/node_modules/ws/lib/websocket.js:595:7)
    at ClientRequest.emit (events.js:315:20)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:641:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
    at Socket.socketOnData (_http_client.js:509:22)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
...

Config

export const Config = {
    protocol: 'https',
    port: 5022,
    cluster: true
}

Info

Every run different amount of tests passes until this error pops up.

Problem with SSL

Hey,
I have generated SSL certificate that is generated by host, not IP in this case I got errors when try to run tests & use the SSL.

Problem

(node:12324) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use `node --trace-deprecation ...` to show where the warning was created)
  Signaling Test
    create
Wed, 17 Mar 2021 07:29:17 GMT uncaughtException:Hostname/IP does not match certificate's altnames: IP: xxx.xxx.xxx.xxx is not in the cert's list: 
Error [ERR_TLS_CERT_ALTNAME_INVALID] [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: xxx.xxx.xxx.xxx is not in the cert's list: 
    at Object.checkServerIdentity (tls.js:297:12)
    at TLSSocket.onConnectSecure (_tls_wrap.js:1507:27)
    at TLSSocket.emit (events.js:315:20)
    at TLSSocket._finishInit (_tls_wrap.js:932:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)