Skip to content
Snippets Groups Projects
Select Git revision
  • 2a6761236f06d8aa6f853e96538c70bb92ccacf0
  • 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
31 results

ice.cpp

Blame
    • Mohamed Chibani's avatar
      2a676123
      ice: decouple instantiation and initialization of ICE transport · 2a676123
      Mohamed Chibani authored and Sébastien Blin's avatar Sébastien Blin committed
      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
      ice: decouple instantiation and initialization of ICE transport
      Mohamed Chibani authored and Sébastien Blin's avatar Sébastien Blin committed
      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
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    net.jami.daemon.metainfo.xml.in 3.51 KiB
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Copyright (C) 2004-2025 Savoir-faire Linux Inc. -->
    <component>
     <id>net.jami.daemon</id>
     <metadata_license>CC-BY-SA-3.0</metadata_license>
     <project_license>GPL-3.0+</project_license>
     <name>Jami daemon</name>
     <name xml:lang="hu">Jami-rendszerfolyamat</name>
     <summary>Privacy-oriented voice, video, chat, and conference platform</summary>
     <summary xml:lang="hu">Adatvédelem-orientált hang-, video-, csevegés- és konferenciaplatform</summary>
    
     <description>
      <p>
       An end-to-end encrypted secure and distributed voice, video, and chat communication platform that requires no central server and leaves the power of privacy and freedom in the hands of users.
      </p>
      <p>
       Jami supports the following key features:
      </p>
      <ul>
       <li>One-to-one conversations</li>
       <li>File sharing</li>
       <li>Audio and video calls and conferences</li>
       <li>Screen sharing in video calls and conferences</li>
       <li>Recording and sending audio and video messages</li>
       <li>Functioning as a SIP phone software</li>
       <li>Distributed architecture — p2p connections, DHT for a peer discovery</li>
       <li>Multi-device support</li>
      </ul>
      <p>
       Client applications for GNU/Linux, Windows, macOS, iOS, Android, and Android TV are available, making Jami an interoperable and cross-platform communication framework.
      </p>
    
      <p xml:lang="hu">
       Végpontokig titkosított biztonságos és elosztott hang-, videó- és csevegés-kommunikációs platform, amely nem igényel központi kiszolgálót, és a felhasználók kezében hagyja a magánélet és a szabadság hatalmát.
      </p>
      <p xml:lang="hu">
       A Jami a következő főbb funkciókat támogatja:
      </p>
      <ul>
       <li xml:lang="hu">Személyes beszélgetések</li>
       <li xml:lang="hu">Fájlmegosztás</li>
       <li xml:lang="hu">Hang- és videohívások és konferenciák</li>
       <li xml:lang="hu">Képernyőmegosztás videohívásokban és konferenciákon</li>
       <li xml:lang="hu">Hang és videó üzenetek rögzítése és küldése</li>
       <li xml:lang="hu">SIP-telefonszoftverként működik</li>
       <li xml:lang="hu">Elosztott architektúra – p2p kapcsolatok, DHT a peer felfedezéshez</li>
       <li xml:lang="hu">Több eszköz támogatása</li>
      </ul>
      <p xml:lang="hu">
       Elérhetők a GNU/Linux, Windows, macOS, iOS, Android és Android TV ügyfélalkalmazásai, így a Jami interoperábilis és többplatformos kommunikációs keretrendszerré válik.
      </p>
    
     </description>
    
     <url type="homepage">https://jami.net/</url>
     <url type="bugtracker">https://git.jami.net/savoirfairelinux/ring-daemon/issues/</url>
     <url type="faq">https://jami.net/help/</url>
     <url type="help">https://git.jami.net/savoirfairelinux/jami-project/-/wikis/home</url>
     <url type="donation">https://www.paypal.com/donate/?hosted_button_id=MGUDJLQZ4TP5W</url>
     <url type="translate">https://www.transifex.com/savoirfairelinux/jami</url>
    
     <provides>
    @PROVIDES_CONTENT@
    ​ </provides>
    
     <!-- https://specifications.freedesktop.org/menu-spec/latest/apa.html -->
     <!-- https://specifications.freedesktop.org/menu-spec/latest/apas02.html -->
     <categories>
      <category>Chat</category>
      <category>Communication</category>
      <category>FileTransfer</category>
      <category>InstantMessaging</category>
      <category>Network</category>
      <category>P2P</category>
      <category>Productivity</category>
     </categories>
    
     <content_rating type="oars-1.1">
      <content_attribute id="social-chat">intense</content_attribute>
      <content_attribute id="social-audio">intense</content_attribute>
     </content_rating>
    
    </component>