v1.3.0

Features:

• Add dark theme with detect system preferred theme
• Add multi language UI. (Supported EN and RU languages with detecting preferred lang)
• New welcome page

Fixes:

• Disable splitting vendor js and css, because very big count small size vendors resources download slowly than 2-4 large resource
• Fix styles on login page
• SignalR: disable Negotiate and set only Websockets transport (at now, proxy sticky session not needed)
• Render UI only when settings and theme helper loaded
• Fix remove user video before select screen for share
• Fix chat styles
• Add participant tracks state check

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

Features:

• Adding Prometheus application metrics
• Adding TURN support and integration with the Coturn server.
• Adding Sentry exception handling (backend and fronend)
• Updated docs and getting started

Fixes:

• Fix video inside participant block in half screen mode
• Fix room name style on small devices
• Fixes related to connecting interlocutors without media elements
• Remove commit hash from version pre-release versions
• Fix PWA colors
• Fix adding participant block to card when it's not created
• Fix forwarding of forgotten arguments.
• Fixing Object and Method Access Errors

Full Changelog: v1.1.0...v1.2.0

1.1.0

Features:

• Added user speaking detection and highlighting it in the conference (using Hark.js)
• Participant volume control
• Refactoring
• Show version
• Default gravatar based on (username + @example.com)

Fixes:

• Fix RTT statistic calc
• Style fixes:
  • Room name style
  • Participants grid style
  • Chat style
  • New log in page style

First release of Peer Meeting

PeerMeeting Release

The first full-fledged release of the service. The following basic functionality has been fully implemented:
Client part:

• full peer then peer conferencing, with the number of participants from 2 to 250 (limitation of p2p connections per tab)
• video conferences
• microphone
• video
• screen sharing
• audio / video mute
• display of participants
• in room chat
• participant control (mute/mute all/kick from room)

Server part:

• Routing WebRTC messages
• Horizontal scaling of the service by connecting to Redis

Ready to use, but better performing load testing to make sure the service is able to withstand the production loads of a particular organization.

Changes relative to the latest candidate release

Client

Features:

• Add participants control menu:
  • mute participant
  • mute all participants
  • kick participant
• Add End call page
• Chat in rooms

Fixes:

• Fix Participant control menu position when half screen mode
• Fix timer where creating blank cards when participant have not card (deleted any stream)

Server

Features:

• Add Chat Hub

Second 1.0.0 release candidate

Client

Features:

1. Add user extra data realtime update and on top of this mechanism transfer the audio muted and video muted state
2. Replace getStats to own implementation webrtc get stats ( it's so light and working in firefox)
3. Add reinitialize stream with new devices when is changed in settings without page reload

Fixes:

1. Fix user extra data when adding participant block
2. Fix exit from half screen when only one people in conference
3. Fix half screen styles in updated Firefox
4. Fix workaround timer who generate empty cards when peer connected but all stream deleted
5. Fix showing video or audio stream from user ( sometimes media track don't getting). New event 'renegotiate-needed' fix this
6. Fix render changes in extra data

Server

Features:

1. Add service scaleout with Redis Backplane

Fixes:

1. Fix signalR limit on messsage (default 32kb but sometimes webrtc messages so fat (38kb)). Now limit 256kb and client reconnect successfully
2. Change logger from microsoft to Serilog. Because only Serilog has async logger (webrtc hub generate more debug messages)

The first candidate for the release of the PeerMeeting service

The first candidate for the release of a peer-to-peer video conferencing service.
Implemented functionality:

1. Backend
   1. Server of routing of client messages (Signaling)
   2. Isolation of messages by room in the signaling server
2. Frontend
   1. Peer-to-peer conferences with the number of users in the room from 1 to 256 (limitation of peer-to-peer connections per tab in chrome)
   2. History of rooms
   3. User avatars from Grafavar
   4. Settings with a choice of devices (poor display of device names in FireFox)
   5. Screen sharing
   6. Pseudo full screen mode, for better viewing of one of the broadcasts
   7. Semi-screen mode - enlarging one of the custom videos and displaying the rest as a list to the right of the video
   8. Displaying the connection status with users (so far only available in chrome-based browsers)
3. Initial documentation for deploying the service (includes a prepared docker-compose file and a pre-configured nginx config with a self-signed certificate for it, for example, also a simple configuration file for docker swarm for use with an external load balancer)

Road map:

1. Displaying the connection status with the user in Firefox
2. Chat
3. Redis backplane for scale the server