Q&A

What is GOnnect and where does it run?

In short	GOnnect is a Linux UC client distributed as a Flatpak that integrates most Desktops via Flatpak portals. GOnnect is designed for Flatpak-based installations and ties into modern desktop environments by using desktop notifications, the system tray, and (e.g on GNOME) the desktop search provider, so everyday communication happens inside your native workflow.
Key points	Linux + Flatpak; integrates via Flatpak portals. Generally Linux-OS-agnostic Desktop integration (notifications, tray, search). Native feel by relying on desktop conventions.
Also asked as	GOnnect overview • Linux UC client • Flatpak-based UC client

What can I do with GOnnect in day-to-day telephony and conferencing?

In short	You can place VoIP calls, transfer, make enquiries, hold up to three-party ad-hoc conferences, and start video conferences as easily as a phone call. Beyond calling, the client centralizes helpful features: access colleagues’ contacts, show status (if available), save favorites, use quick access via the system tray, integrate with GNOME desktop search, register as URL handler for `tel:`/`sip:`, toggle queue logins, start a Jitsi conference or hand over an active VoIP call to Jitsi, and control media playback.
Key points	VoIP calls, transfer, enquiries, three-party ad-hoc conference. Video conferences started like calls. Contacts, status, favorites, tray quick access. GNOME search, URL handler `tel:`/`sip:`. Queue login toggle; Jitsi start/upgrade; media control.
Also asked as	Daily features • Calling & Jitsi in GOnnect • Softphone capabilities

Which distributions and desktops are known to be supported?

In short	Any distribution that supports Flatpak is known to be supported. Because GOnnect depends on desktop notifications, system tray and other desktop features via Flatpak portals, environments that provide these components in a standard way deliver the best experience.
Key points	Flatpak support required. Supports virtually every desktop. Best results where tray/notifications are available.
Also asked as	Supported distros • GNOME/KDE support • Flatpak requirements

What are the requirements — and why do notifications and the system tray matter?

In short	Without notifications, incoming calls are still possible, but you will not see a pop-up reminder and have to open the call window yourself. Without a system tray, the application must also be brought to the front manually. Both features are not strictly required, but they make call handling far more convenient.
Key points	Works without notifications and tray, but less convenient. Notifications → instant call pop-ups. Tray → quick access and window control.
Requirements	Desktop notifications; system tray.
Not included	Alternative signaling paths outside desktop conventions.
Also asked as	Why enable tray? • Call notifications • Desktop prerequisites

How is GOnnect configured, and what happens if no configuration is present?

In short	GOnnect is designed for managed environments, where configurations are centrally provisioned by the IT-department. This ensures consistent SIP and VoIP settings across the organization, reduces errors, and lowers support effort. The client does not include a manual SIP dialog by design, because provisioning makes deployment faster and more reliable. If no configuration is present, GOnnect offers a preset dialog to help you get started.
Key points	Central provisioning = consistent setup across all desktops. No local SIP dialog → less user error, less support overhead. Preset dialog available if no config is found.
Benefits for organizations	Faster rollout at scale. Easier maintenance by VoIP experts. Uniform standards across the company.
Requirements	Provisioned configuration available.
Not included	In-app SIP registration UI.
Also asked as	Configure GOnnect • No SIP dialog • Provisioning flow

How do I install GOnnect and prepare my desktop?

In short	GOnnect is distributed only as a Flatpak and therefore runs on all Linux desktop environments that support Flatpak. You install via your distribution’s software manager (for example KDE Discover, GNOME Software, or another Flatpak front-end). On GNOME, some extra preparation is recommended to enable the tray and desktop search integration. Install through your software manager by searching “GOnnect” and choosing Install. On GNOME, make the following adjustments:
Steps (GNOME only)	Enable system tray: Open Extensions → activate AppIndicator and KStatusNotifierItem Support. Set default tel:/sip: app: Settings → Apps → Default Apps → set Calls to GOnnect. Enable desktop search: Settings → Search → enable GOnnect → adjust result order if needed.
Key points	Available only as Flatpak package. Runs on all Linux desktops (KDE, GNOME, Xfce, etc.). Installation via your Flatpak software manager. GNOME requires additional steps for tray & search integration.
Requirements	Flatpak runtime. On GNOME: AppIndicator/KStatusNotifierItem extension for tray.
Not included	Installation outside of Flatpak (no native DEB/RPM)
Also asked as	Install GOnnect on Linux desktops • Flatpak installation of GOnnect • Enable GNOME tray and search integration • Set default dialer for tel:/sip: URIs

How do I start the app and bring up the main window?

In short	Launch GOnnect from the application menu/launcher, from your desktop’s search (on GNOME this includes integration with desktop search), by following a tel:/sip: link, or via the command line with flatpak run de.gonicus.gonnect. By default the app starts in the background unless showing the main window on startup is enabled. Look for the GOnnect icon in the system tray; open it and choose Tray → Dial… to bring up the main window. See First start.
Key points	Starts from launcher, desktop search, URI, or CLI. Background start by default (optional main-window on startup). Tray menu path: Tray Dial…
Also asked as	Start GOnnect • Open dial window • CLI launch • Run GOnnect from system tray • Launch via tel:/sip: link

How do search, dialing, history, favorites and outgoing identity selection work?

In short	Use the top search/dial input; pick a result or call the number; history and favorites offer quick call-backs, and the outgoing identity dropdown applies to the next call only. Type a number and choose Call… or type a name and pick a search result; fuzzy search helps match names like “Jon Do” → “John Doe.” History supports double-click to call; mark favorites via context menu. The identity dropdown sits bottom-left of the results and changes only the next call; set defaults in Settings Telephony settings / Preferred identities. See Main window.
Key points	Search/dial input with fuzzy search. History (double-click) and favorites. Outgoing identity: per-next-call; default in Settings.
Also asked as	Fuzzy search dialing • Set outgoing identity • Favorites & history

How do I place, receive and manage multiple calls—including tones, ad-hoc conferencing and forwarding?

In short	Start calls from search/history/favorites/tray/GNOME search/URI/CLI; manage active calls in the call screen, send DTMF with number keys, and with exactly two active calls you can create a three-party conference or forward via drag-and-drop. Incoming calls appear as desktop notifications to accept or reject; existing calls are automatically put on hold when you accept or start another. A three-party conference is hosted by the client that created it; the host’s connection or exit affects other participants. Forwarding works by dragging one person onto the other in the right-hand list. See Calls, Active call(s), DTMF (dial tones), Incoming calls, Multiple calls.
Key points	DTMF: press number keys while call is focused. Multiple calls auto-hold on accept/start. 3-party conference (exactly two active calls). Forward by drag-and-drop in the persons list.
Requirements	Exactly two active calls for ad-hoc conference.
Not included	Server-side conference hosting inside GOnnect (host is the initiating client).
Also asked as	DTMF tones • 3-way call • Call forwarding

Which settings can end users adjust (appearance, behavior, audio, debugging)?

In short	User-facing settings cover main-window on startup, notification button order, Jitsi chat notifications, USB headset driver options, bring-to-front on pickup, appearance and color scheme, busy signaling, preferred identities, audio environments, and a timed debug mode with log download. Open settings via the tray, the app icon, or the bottom-left button. Appearance includes custom window decorations, dark tray icon, and a color scheme with “system default.” Telephony behavior covers busy signaling during active calls and managing preferred identities (default behavior, auto-selection by prefix, or specific identity). Audio uses environments triggered by device changes; choose input/output, ringtone device, and ringtone. Debug mode restarts with increased logging for five minutes and allows log download; LDAP contacts can be reloaded manually. See Configuration and settings, Generic settings, Appearance, Telephony settings, Preferred identities, Audio settings, Debugging.
Key points	Main-window on startup; invert Accept/Reject; Jitsi chat as notifications. USB headset driver + optional mute propagation toggle; bring-to-front on pickup. Window decorations; dark tray icon; light/dark/system color scheme. Busy signaling; preferred identities (default/auto/specific). Audio environments; input/output/ringtone; debug mode (5 min) + log download; reload LDAP contacts.
Also asked as	Change color scheme • Preferred identity rules • Enable debug logging