FAQ

To jest lista najczęściej zadawanych pytań (FAQ), włącznie z pewną ilością pytań technicznych.

Pytania z Forum też są tu dodawane.

Podstawy

Co to jest Jami?

Zobacz Introduction.

Co to znaczy Jami?

The choice of the name Jami was inspired by the Swahili word jamii which means community as a noun and together as an adverb. It was chosen as it reflects the vision for the project:

  • a free/libre program available to all that helps bring communities together,

  • jest wspierany przez społeczność i

  • respektuje wolność i prywatność użytkowników

Jak mogę zrobić raport?

Please see the Bug report guide.

Co czyni Jami różniącą się od innych platform komunikacyjnych?

Jami nie działa jak większość platform komunikacyjnych, ponieważ jest rozproszona:

«Image: Centralized, decentralized, and distributed network topologies»

Some of the consequences may seem surprising. For instance, since accounts are stored on the user’s device, passwords are optional. However, the most significant practical differences are that the user has more freedom and privacy.

Co znaczą zielone/pomarańczowe/czerwone kółka statusu obok zdjęć profilów?

On a user’s account, 🔴 (a red circle) displayed means that the device is not connected to the DHT or is offline. A detailed error should be displayed explaining the issue. Checking the network/Internet connection or restarting the app may resolve the issue.

Dla kontaktów:

  • no circle displayed means that no device is detected on the DHT. The contact is unreachable.

  • 🟠 (an orange circle) displayed means that at least a device is announced on the DHT, so the contact SEEMS to be reachable. The device does not have a direct connection towards this peer yet. But they should be able to receive connection requests. Because the device is not directly connected to anything, the device status is unable to be determine for sure. So this can be translated to „Seems to be reachable”, but connection may fail (firewall, deadlock, NAT, etc). The presence generally have a TTL of:

  • 🟢 (zielone kółko) znaczy, że to urządzenie jest połączone z urządzeniem tego urzytkownika..

Dlaczego brakuje mi funkcji u mojego klienta?

Not every client implements all features. Check the All features by client list to see if the client is missing the feature. Feature requests can be made at https://git.jami.net.

Czy Jami wspiera potwierdzenia przeczytania wiadomości? Jak je włączyć, wyłączyć?

Tak. Potwierdzenia przeczytania wiadomości są dostępne w Jami na desktopie, Android, Android TV oraz iOS.

Does Jami support typing indicators? Can I turn them on or off?

Yes. Typing indicators can be enabled or disabled in the settings on Jami for Desktop, Android, and iOS.

Mogę podzielić się ekranem?

Yes. Screen sharing is available on Jami for Desktop and Jami for Android. To activate screen sharing, click the „Share screen” button while in an audio or a video call.

Mogę rozmawiać na konferencji grupowej?

Yes. Jami contacts can be added to (audio or video) calls by clicking the „Add participant” button.

Czy Jami obsługuje rozmowy grupowe?

Tak.

Dlaczego moje przesłane wiadomości nie pojawiają się na wszystkich połączonych urządzeniach?

Before the implementation of Swarm Technology, an account’s devices would only receive the same messages from contacts if the device was online at the time of the message being sent. However, sent messages would not show up on devices other than the one sending the message.

With the implementation of Swarm Technology, conversation histories of new conversations (including one-on-one conversations) are fully synchronized between all of an account’s linked devices. Please upgrade all old versions of Jami to the latest version that includes Swarm Technology. The latest version of Jami is always available from the Download page of the Jami website, at https://jami.net/download/.

To learn more about Swarm Technology, visit the blog post Synchronizing conversation history with Swarm and visit the Developer manual.

Mogę przesłać wiadomości do kontaktów offline?

With Swarm Technology conversations, every device stores a copy of all of the messages in that conversation. If a user’s, or another participant’s, device is unreachable when a message is sent, when it becomes reachable, it will try to fetch any new messages from other reachable devices and synchronize message history. This can be done whenever at least one other device that has a copy of the new messages is also reachable.

Zobacz także

To read more about how conversations using Swarm Technology are synchronized, visit the blog post Synchronizing conversation history with Swarm.

If the participants in a conversation are often not online at the same time (for instance, due to different time zones), one of them might choose to set up Jami on an often-online device. The often-online device would receive the messages from each participant and relay them to the others whenever they come online. Thus, Jami acts like a „server” while remaining completely distributed by nature.

Zobacz także

To set up Jami on often-online devices, visit the Jami on servers page.

Gdzie znajdują się pliki konfiguracyjne?

Jami zapisuje swoją konfigurację (polityka, certyfikaty, historia) w różnych miejscach w zależności od platformy.

  • GNU/Linux: global configuration is under ~/.config/jami/dring.yml, and account-specific files are under ~/.local/share/jami/. Finally, there is a cache directory at ~/.cache/jami/.

  • macOS: the full configuration is under ~/Library/Application Support/Jami/ if installed via https://jami.net. The app store version uses ~/Library/Containers/com.savoirfairelinux.ring.macos/Data/Library/Application Support/jami/.

  • Android: the full configuration is under /data/data/cx.ring/ (may require root privileges to view or change from outside Jami).

  • Windows: global configuration is under %AppData%/Local/jami/dring.yml, and account-specific files are under %AppData%/Local/jami/. Finally, there is a cache directory at %USERPROFILE%/.cache/jami/.

Informacja

Audio and video messages are recorded in the local-data in the folder: sent_data

For files, if a file is saved (right-click on the file, then Save), it will be added to the directory configured in the application settings.

How much bandwidth is required for calls?

For audio calls, Jami uses about 100 Kbps. For a video call, about 2 Mbit/s is required for medium quality. If the connection is slower, the bitrate will be automatically reduced.

If a device is hosting a video conference, approximately an additional 2 Mbps per participant is required. So, for example, for a conference with 10 participants, each participant requires 2 Mbps up and down, and the host requires 20 Mbps up and down.

Jami wykorzystuje również algorytm do zmiany zużycia w zależności od jakości połączenia.

How can Savoir-Faire Linux Inc. (SFL) afford to give Jami away for free? How does SFL make money with Jami?

Savoir-Faire Linux Inc. (SFL) is a consulting company with some R&D projects. Jami is a GPLv3+ project and this will not change. SFL already sells services for several fields of expertise (hosting, developing websites and applications, embedded software, etc).

Jami jest finansowane na wiele sposobów:

Stałe wydatki Jami:

  • Jako system rozproszony, Jami z założenia ponosi bardzo niskie koszty

  • Zbieranie anonimowych statystyk może zostać dodane w przyszłości, aby lepiej zrozumieć korzystanie z Jami; jednak żadne dane osobowe nie będą gromadzone.

Zarządzanie kontami

Co to jest rachunek Jami?

A Jami account is an asymmetric encryption key. The Jami account is identified by a Jami ID, which is a fingerprint of the public key.

What information is required to be provided to create a Jami account?

When a new Jami account is created, private information like an email address, address, or phone number is not required.

Możemy dostarczyć następującą informację:

  1. Zdjęcie profilowe (opcjonalnie).

  2. A display name (optional), which is the name that clients will display for your contact. It can contain special characters.

  3. A username (optional), which is a unique identifier that is directly associated with your Jami ID. This username→Jami ID mapping is stored on a server (ns.jami.net by default, but you can host your own).

  4. A password (optional). This password is used to protect the account archive in the device.

Zobacz także

More information about Jami accounts is available in the Account management section of the Developer manual.

Gdzie jest mój dowód?

The Jami ID is displayed on the main page of the Jami app. The Jami ID is a 40-character string of letters and numbers; for example: f2c815f5554bcc22689ce84d45aefdda1bce9146.

Dlaczego nie muszę używać hasła?

On a centralized system, a password is required to authenticate with a public server where accounts are stored. Any third-party who knows a person’s password could steal the person’s identity.

With Jami, the account is stored in a folder on the device. There is no public server where Jami accounts are stored. Hence, an account password is not required with Jami. The password is only used to encrypt a Jami account in order to protect the Jami account from someone who has physical access to the device.

A password may not be wanted or required if the device is encrypted. Recent versions of Jami do not ask for an account encryption password by default when creating new accounts.

Informacja

Changing a password will only change the password on the current device and it’s not synced (because there is no server and other devices can be offline anyway).

Dlaczego nie muszę zarejestrować nazwy użytkownika?

The most permanent, secure identifier is the Jami ID. However, these are difficult to use for some people, there is also an the option of registering a username. Username registration requires a name server, such as Jami’s default one at ns.jami.net.

Jeśli nie zarejestrujesz nazwy użytkownika, możesz ją zarejestrować w dowolnym momencie.

If you host your own name server at example.com, usernames registered there can be looked up by searching for username@example.com.

Mogę zmienić nazwisko?

Usernames are unable to be changed on the default name server (ns.jami.net).

Jaka jest różnica między nazwą użytkownika a nazwą wyświetlania?

The username can be used as an identifier. The username points to the Jami ID, which is the permanent, secure identifier. Usernames are unique on the name server.

A display name allows you to choose another name that identifies a Jami account to contacts. Display names can be edited or changed at any time and only trusted peers can see them.

Jak mogę zawrzeć konto?

Są 2 sposoby stworzenia kopii zapasowych konta:

  1. Link another device to the account so the account will be on two devices. This option is available in the Account settings page.

  2. Back up the account archive. More information about Jami accounts is available in the Account management section of the Developer manual. Some clients allow exporting the Jami account archive from Account settings.

Mogę odzyskać nazwisko bez kluczy?

If the default name server at ns.jami.net stores a username, the username cannot be retrieved without the key. There is no way to prove a username without the key.

If a different name server was used to store a username, there may be a way to move the username to a new Jami ID at the discretion of the administrator of the name server.

Zobacz także

More information about name servers is available in the Name Server protocol section of the Developer manual.

Czy mogę odzyskać konto, jeśli zapomnę hasło?

No. There is no traditional account recovery process; the user is the only person with access to the user’s data.

Wypominek

Use a password manager if there is a concern about forgetting the Jami account password.

Co się stanie, gdy usunę konto?

Konto Jami jest przechowywane jedynie w urządzeniach z kontem Jami.

Konto Jami jest usunięte i nie da się go odtworzyć, jeśli:

  • nie ma kopii zapasowej konta Jami i

  • konto Jami jest usunięte ze wszystkich urządzeń.

Na dodatek, nikt inny nie może użyć konta Jami.

The contacts will still have the messages which were sent to them, but all public record of the account on the DHT will eventually disappear due to absence and lack of activity.

Ostrzeżenie

The default ns.jami.net name server does not delete any registered usernames – other name servers might (not recommended), at their administrator’s discretion. So, if an account has a registered username on the default name server and the account is deleted or lost (without a backup), nobody (including the user) will be able to register a new account with that username again; thus, nobody can reach the user at that username anymore.

Żeby nie stracić konta Jami please zrób kopię zapasową!

Zaawansowane

Jaki protokół używa Jami do szyfrowania od końca do końca?

TLS (Transport Layer Security) protocol version 1.3 is used with a perfect forward secrecy requirement for the negotiated ciphers for calls and file transfers. Messages are encrypted with an RSA key.

Jakie dane przechodzą przez moją maszynę, gdy uczestniczę w sieci Jami?

All these data are encrypted. There is:

  • deskryptory ICE innych użytkowników Jami (ICE to protokół, który pomaga nawiązać komunikację między dwoma komputerami)

  • niektóre wiadomości tekstowe

  • Konta, które są obecnie połączone z nowym urządzeniem, jak wyjaśniono powyżej.

Audio/video streams and some text messages pass through the VoIP protocol. Text messages can be sent either via VoIP or DHT (the distributed network), depending on whether a VoIP communication channel is already open or not.

Dlaczego jestem w stanie komunikować się ze sobą?

Many users use Jami to transfer data from one device to another. A benefit of transferring data using Jami is that no third-party server is required.

Wypominek

This is one of the many unique features of Jami.

Add yourself as a contact to enable:

  • Peer-to-peer (without a third-party server) file transfers between your devices.

  • Calling your account on other devices if you forget where the device is.

  • Having one account shared in a family or organization to answer calls from shared contacts.

  • Calling yourself to talk with members in the family or organization who are at different locations.

  • Writing notes and lists to yourself that are available on all your devices.

  • Other use cases that are not listed here.

Mam włączyć powiadomienia push?

Push notifications allow Jami to operate in a way more adapted to the context of mobility (energy consumption, data, …). However, for the moment, notifications go through Google’s servers, via the Firebase service. Only one identifier is transferred and it is unusable for anyone who does not have access to the account.

Co to jest serwer bootstrap?

A bootstrap server provides an entry point to a distributed network. To connect to a network, Jami must know one other node. This is the role of the bootstrap. It can be any node in the network, but bootstrap nodes are generally always up and available. The default Jami bootstrap is the bootstrap.jami.net server.

Co to jest serwer TURN? Co to jest STUN?

A TURN server is a relay and is generally used when two peers are unable to contact each other due to some firewall restriction, have NAT without any open port, and no IPv6.

A STUN server is only used for SIP accounts and is generally used to obtain the public IP address of the device. For Jami accounts, the DHT already provides the public IP address of the device.

Co to jest DHT proxy?

The DHT proxy is a server that registers on the DHT network on behalf of the device and relays information to and from the device. Thus, it is the server that will be active on the DHT network and will participate in the network, and no longer the target device. Multiple devices can register on the same DHT proxy.

Ogólnie rzecz biorąc, aby przenosić dane między dwoma rówieśnikami, istnieją 3 kroki:

  1. Exchange candidates (IP addresses) via the DHT network.

  2. Negotiate the best P2P channel between the peers.

  3. Przekaż dane na tej zbiorze.

The DHT proxy is only used for the first step.

What if I disable the DHT proxy on Android, and what about push notifications?

There are 3 modes on how to use the Android application:

  • With push notifications (DHT proxy must be enabled). This mode supports notifications for Android (via Google/Firebase, UnifiedPush, or Apple/APN). This decreases battery usage by removing the sync required with the DHT and without any socket always alive.

  • Without push notifications but with DHT proxy enabled. This avoids the application synchronizing with other nodes, but „Run in the background” MUST be enabled to avoid the operating system killing the application.

  • Without DHT proxy. In this case, „Run in the background” MUST be enabled to avoid the operating system killing the application. The application will synchronize with the other DHT nodes.

Nadal mam problemy z aplikacją Android nawet jeśli optymalizacja baterii jest wyłączona

Please read https://dontkillmyapp.com for more details. If it does not solve the issues, please open a bug report (ideally with a scenario to help reproduce and/or logs).

Jak działa usługa rejestracji nazw użytkownika?

With the default name server (ns.jami.net), the usernames are registered on an Ethereum blockchain. It is possible to develop a name server with any underlying data storage technology. For example, an SQL database could be used instead of a blockchain for the data storage technology.

With the default name server, look up usernames with https://ns.jami.net/name/test, where test is a username for which we are looking for a matching Infohash.

Once registered, the name server does not provide any way to remove the mapping.

More information about name servers is available in the Name Server protocol section of the Developer manual.

Jak mogę zmienić termin rozmowy?

In the dring.yml file (see Gdzie znajdują się pliki konfiguracyjne?), the ringingTimeout value, measured in seconds, can be changed.

Jak kopiować i ponownie importować rozmowy i konta

Informacja

This is only applicable for Desktop clients. Desktop clients run on GNU/Linux, macOS, and Windows operating systems.

  1. Export each account. (For GNU/Linux: Open settings → Account → Manage account → Backup account).

  2. Skopiej i zapisz bazę danych (np. w ~/.local/share/jami/).

  3. On the new device, to import the settings and contacts with empty conversations:

    • If Jami is opened for the first time, import the archive backup. I already have an account → Import from an archive backup.

    • If Jami already has an account, import each archive backup. Add another account → I already have an account → Import from an archive backup.

  4. Close Jami and replace the database with the database previously saved.

Jak bezpieczny jesteś?

TLS/SRTP is used to secure connections and communications over the network.

SRTP over SIP is implemented using recommendations described in the following two RFCs:

Typically 2 kinds of sockets are negotiated. One for the control socket, the other for the media sockets.

Typical control session will use the following cipher suite:

(TLS1.3)-(ECDHE-SECP384R1)-(RSA-PSS-RSAE-SHA384)-(AES-256-GCM)
(TLS_ECDHE_RSA_AES_256_GCM_SHA384)

DTLS (fallback) supported:

"SECURE192:-KX-ALL:+ANON-ECDH:+ANON-DH:+SECURE192:-VERS-TLS-ALL:+VERS-DTLS-ALL:-RSA:%SERVER_PRECEDENCE:%SAFE_RENEGOTIATION"

TLS:

"SECURE192:-KX-ALL:+ANON-ECDH:+ANON-DH:+SECURE192:-RSA:-GROUP-FFDHE4096:-GROUP-FFDHE6144:-GROUP-FFDHE8192:+GROUP-X25519:%SERVER_PRECEDENCE:%SAFE_RENEGOTIATION"

Podpłacane krypto-swiaty do sesji medialnej to:

  • AES_CM_128_HMAC_SHA1_80 / SRTP_AES128_CM_HMAC_SHA1_80

  • AES_CM_128_HMAC_SHA1_32 / SRTP_AES128_CM_HMAC_SHA1_32

When do public IP addresses get exposed?

Three main connectivity scenarios are considered: (1) a classic configuration, (2) behind a VPN, and (3) via Tor.

As Jami is a P2P application, the reader would probably know that (2) or (3) is mandatory to avoid IP address leaking.

Moreover, even if it’s my answer, you can choose to not trust my answer and check the code, or use Wireshark or other tools. Generally, Jami developers use the first scenario (sometimes the second one). It is impossible for the Jami developers to test all possible network configurations. If you discover a bug, please open an issue.

For all three scenarios, there are three main actions:

  • wysyłanie wiadomości (w tym wykorzystuje DHT);

  • sending a file (TCP ICE connection as described in the File transfer section of the Developer manual; and

  • placing a call (TCP + UDP ICE connection as described in the Calls section of the Developer manual.

(1) Konfiguracja klasyczna

Wyślij wiadomość

The Jami application is running a DHT (https://opendht.net) node on your device. So every operations on the DHT will use your IP address. This is why Jami has the option to use a DHTProxy (e.g., http://dhtproxy.jami.net/); this will avoid using your node and instead will use another node on the network (which will see your IP address). Note that your message is not sent directly to the other device. In fact your message is sent on some nodes of the DHT and your contact will retrieve the message on this node. So, your contact don’t see your IP address at this step, but the node who get the message will (or they will see the IP address of the proxy).

Wyślij plik

As described in the docs, you will send a message with all the IP address you know that your peer can contact in an encrypted packet. So, if your peer send you a file or you send a file, your addresses will appear in the ICE message.

Rozmowy

Tak jak powyżej, adres IP istnieje w ICE.

(2) Za VPN’em

Wyślij wiadomość

The IP address of your VPN will be used by the DHT node. If you want a proof, you can compile dhtnode and run the la command to get your public detected address. This is what I got:

./tools/dhtnode -b bootstrap.jami.net
Bootstrap: bootstrap.jami.net:4222
OpenDHT node be58fdc9f782269bfc0bbfc21a60bca5f02cb881 running on port 54299
(type 'h' or 'help' for a list of possible commands)

>> la
Reported public addresses:
IP ADDRESSES OF MY VPN

So, if you don’t use a proxy, your VPN addresses will be used for using the DHT. If you use a DHTProxy, the DHTProxy will see your VPN addresses.

Wyślij plik

Tak jak powyżej, ICE zawiera:

  • adresy z sieci LAN

  • adres publiczny Twojego VPN

  • adres TURN, jeśli adres TURN jest włączony

Zadzwoń.

Same as above, your public address is replaced by your VPN address. You can see it in the logs from daemon. See Płoty.

(3) Tor

Wyślij wiadomość

Tor zasadniczo nie obsługuje UDP. To oznacza, że nie możesz używać węzła DHT lokalnie, musisz użyć DHTProxy.

Wyślij plik

Wykonałem przesyłkę plików z Jami + TOR.

[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a8c801 1 TCP 2130706431 192.168.200.1 33293 typ host tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a8c801 1 TCP 2130706431 192.168.200.1 9 typ host tcptype active
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a80103 1 TCP 2130706431 192.168.1.3 33293 typ host tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a80103 1 TCP 2130706431 192.168.1.3 9 typ host tcptype active
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: R33fe279d 1 TCP 16777215 51.254.39.157 27427 typ relay tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Sc0a8c801 1 TCP 1694498815 185.220.101.24 33293 typ srflx tcptype passive

Pierwsze są jakieś 192.168.x.x więc nie obchodzi nas. 51.254.39.157 to adres TURN we Francji (moje urządzenie jest w Kanadzie). 185.220.101.24 to węzeł wyjścia Tor:

inetnum:        185.220.101.0 - 185.220.101.127
netname:        MK-TOR-EXIT
Zadzwoń.

To nie zadziała (w rzeczywistości można utworzyć połączenie sterowania SIP, ponieważ jest to połączenie TCP), ale media są negocjowane w UDP, więc to się nie uda.

Jakie porty używa Jami?

Jami działa jako serwer i otrzymuje nowe porty dla każdego połączenia (bezpośrednio związane).

  • dht: UDP [4000, 8888]

  • Audio: UDP [16384-32766]

  • Wideo: UDP [49152-65534]

  • Kontrola SIP: UDP/TCP włączone losowo

Informacja

If UDP is blocked, a DHTProxy can be used to use TCP instead. However, media will not work because it only supports UDP.

So for UFW (Uncomplicated Firewall), it is recommended to open the Terminal and enter the command:

sudo ufw default allow outgoing

Currently, it is not possible to define the range of configured ports to be used by Jami. The inbound traffic can be controlled without issue; Jami should work and can use a TURN server if required.

If you run your own proxy or name server:

  • DHTProxy, name server: TCP [80-100], 443

Jeśli uruchomicie własny serwer TURN:

  • TURN/STUN: TCP+UDP 3478, 5349

Czy można użwywać Jami w sieci lokalnej (LAN) bez dostępu do internetu?

Yes! Thanks to Jami’s architecture, Jami users on a local/private network can communicate among themselves using Jami, without requiring any outside connectivity such as the Internet.

To do so, from Jami’s Account settings open Advanced account settings. There, enable the Enable local peer discovery setting. Additionally, you may want to manually set the bootstrap node’s address (default: bootstrap.jami.net) to the IP address of another device on your network that also runs Jami and/or an OpenDHT node.

Informacja

If you will use this Jami account for communicating only with only with other devices on the same local/private network, you can disable TURN if you wish. If you do so, and later you decide to use this account also for communicating with other Jami devices outside your network, don’t forget to enable TURN again, as it helps Jami work around issues with some overly restrictive firewalls.

Jak mogę jeszcze bardziej skonfigurować kodek?

Codecs can be configured via a file. In the configurations files, you can create a file called encoder.json like this:

{
    "libx264": {
        "profile": 100,
        "level": 42,
        "crf": 20,
        "preset": "ultrafast"
    },
    "h264_vaapi": {
        "low_power": 1
    },
    "libopus": {
        "application": "voip"
    }
}

lub:

{
    "libopus": {
        "bit_rate": 128000
    }
}

This file is located in the same directory as dring.yml.

To check which options are supported, use the command ffmpeg -h encoder=[encoder_name], where encoder_name can be any of libx264, libvpx, mpeg4, h263, libopus, libspeex, g722, pcm_alaw, or pcm_mulaw (the FFmpeg names for all of Jami’s supported encoders).

Jak mogę skonfigurować procesor dźwiękowy?

An audio processor allows Jami to clean up and process your microphone’s audio. It can remove echo, reduce noise, and equalize your microphone’s volume. Additionally, it can detect when you’re speaking and send this information to participants in your call. The audio processor settings can be set in your dring.yml file. See this section to find where this file is located.

Odpowiednie klucze preferencyjne to:

  • audioProcessor, which configures which audio processor to use. The valid options are:

    • webrtc: the WebRTC Audio Processing library <https://www.freedesktop.org/software/pulseaudio/webrtc-audio-processing/>_

    • speex: the Speex DSP library <https://gitlab.xiph.org/xiph/speexdsp>_

    • null: disables audio processing (though your system echo canceller may still be used, see below)

  • echoCancel, which configures how echo cancelling should be done. The valid options are:

    • auto: try to use your operating system’s echo canceller (if it exists), otherwise fall back to the chosen audio processor’s echo canceller

    • audioProcessor: only use the chosen audio processor’s echo canceller

    • system: only use your operating system’s echo canceller

    • null: don’t do any echo cancelling

  • noiseReduce, true/false to set noise reduction on the audio processor

  • automaticGainControl, true/false to set automatic gain control on the audio processor

  • voiceActivityDetection, true/false to set voice activity detection on the audio processor