Skip to content
Snippets Groups Projects
  1. Oct 08, 2020
  2. Oct 07, 2020
  3. Oct 06, 2020
  4. Oct 02, 2020
  5. Oct 01, 2020
  6. Sep 30, 2020
  7. Sep 29, 2020
  8. Sep 28, 2020
    • Pedro Beschorner Marin's avatar
      Patch of improvements for bbb-web · 2fb26ff0
      Pedro Beschorner Marin authored
      This patch includes two improvements made for bbb-web. It tries to better isolate
      the sessionToken's handling and session's validation, including logs for each one of
      these steps; and removes maxParticipats control from registered users (that are no
      longer removed from bbb-web collections) binding it to joined users or users that
      reached the enter API call. The following adds more details about this last one:
      
      User's regular flow to join a meeting goes around an API join call -> redis register event ->
      redirect to client page -> API enter call -> redis join event. When the guest policy is ASK_MODERATOR,
      non-moderators are registered and redirected to a guest lobby that polls for her/his guest status and
      only enters the meeting after a moderator approval.
      Using registered users as control to check how many participants are in a meeting is problematic because
      non-approved guests are counted as participants and bbb-web has to find out when to ditch registered users
      records to make a seat in a meeting available again. In other words, a meeting with maxParicipants
      of 5 can get it's joins locked with a moderator and 4 waiting guests or bbb-web can wrongly drop a registered
      user record on a reconnection inducing weird 401 responses from the API.
      
      This change proposes to control maxParticipants both at join and enter API calls monitoring the number
      of redis joined users. This also includes an extra buffer to capture users that called the enter API but
      still don't have an user joined event.
      User left events are now handled different holding the user data before removing from the joined users collection
      and only releasing after verifying that the user didn't reconnected.
      
      Both user left timeout `usersTimeout` and entered user timeout `enteredUsersTimeout` can be configured at properties.
      2fb26ff0
  9. Sep 25, 2020
    • Mario Jr's avatar
      Add sessionDescriptionHandlerModifiersPostICEGathering option to SIP.js INVITER · 2d2a0347
      Mario Jr authored
      Current sessionDescriptionHandlerModifiers of SIP.js acts before ICE gathering is done. This means we are not able to modify/strip candidates in local SDP.
      This modifier acts on local SDP, by allowing user to modify SDP before it is sent on INVITE message.
      2d2a0347
    • Mario Jr's avatar
      Port SIP.js to 0.17.1 release · 619ffa0e
      Mario Jr authored
      This considerably changes the way we process audio signaling and start audio elements in user's browser.
      We now avoid using AudioContext element for both microphone and listenonly calls, once it is unstable for some iOS devices (cracky audio, user stops hearing audio after a while).
      Increased default value for listenOnlyCallTimeout: this avoids activating FreeSWITCH's fallback when ICE negotiation takes longer than 15sec (tested on DO).
      Increased listenonly logs.
      This fixes #8133 #10388
      619ffa0e
    • Dixon Fred's avatar
      Merge pull request #10533 from kepstin/rec-fixes · 78ced5d4
      Dixon Fred authored
      Recording: Skip shapes with missing "thickness" attribute
      78ced5d4
    • Anton Georgiev's avatar
      Bump up to 2.2.27 · bc478104
      Anton Georgiev authored
      bc478104
Loading