Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • release/202005
  • release/202001
  • release/201912
  • release/201911
  • release/releaseWindowsTestOne
  • release/windowsReleaseTest
  • release/releaseTest
  • release/releaseWindowsTest
  • release/201910
  • release/qt/201910
  • release/windows-test/201910
  • release/201908
  • release/201906
  • release/201905
  • release/201904
  • release/201903
  • release/201902
  • release/201901
  • release/201812
  • 4.0.0
  • 2.2.0
  • 2.1.0
  • 2.0.1
  • 2.0.0
  • 1.4.1
  • 1.4.0
  • 1.3.0
  • 1.2.0
  • 1.1.0
30 results

src

  • Clone with SSH
  • Clone with HTTPS
  • Mohamed Chibani's avatar
    Mohamed Chibani authored
    Instantiation and initialization of ICE are done in a single
    stage (in the class constructor).
    To initialize the ICE instance, connection information must
    first be gathered asynchronously.
    However, when sharing ICE media instance between subcalls,
    it's better to have a valid ICE instance as soon as possible
    (even if not fully initialized) to proceed with the call
    initialization process, then wait for ICE initialization to start
    the call.
    Thus, the ICE instantiation will be performed synchronously as
    soon as the parent (main) call is created, then it will be
    initialized asynchronously when the connection info are ready.
    
    Gitlab: #619
    
    Change-Id: I9c97516238f1a690603975ec968c8c6733155d4a
    2a676123
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    Name Last commit Last update
    ..