VoIP.infoThe independent guide to business communications.
VoIP.info Client research

Jitsi Desktop: legacy SIP client and maintenance boundaries

Keep the community-maintained Jitsi Desktop SIP client distinct from Jitsi Meet, and treat its legacy packages and documentation as migration evidence rather than a default new deployment.

Reviewed 2026-10-07Jitsi Desktop project repository and release archive, legacy download and setup pages, registrarless SIP guide and current Jitsi user FAQ reviewed October 7, 2026; no installer, package signature, operating system, Java runtime, account, credential, registrar, PBX, NAT path, audio device, protected session, message, desktop share, emergency workflow, availability, compatibility, price or call was inspected or testedAdvancedDocumentation based · not lab tested

Do not confuse Jitsi Desktop with Jitsi Meet

The project repository describes Jitsi Desktop as an audio, video and chat communicator with SIP and XMPP support, while the current Jitsi FAQ identifies it as the older application from which Jitsi's conferencing work evolved. Jitsi Meet, its browser and Electron clients, Jigasi and the desktop SIP client are different products and paths. A current Jitsi Meet release does not update or certify Jitsi Desktop.

Record the exact executable, release tag, operating system, Java runtime, installer source and SIP account before investigating behavior. Search results and old pages that say only “Jitsi” can refer to different generations. Keep meeting-room features, browser permissions and server-side SIP gateways out of a desktop-client acceptance plan unless they are separately in scope.

Treat maintenance status as a deployment constraint

The repository says Jitsi Desktop is not actively developed and that improvements, bug fixes and builds depend entirely on community contributions. The current Jitsi FAQ similarly says it is no longer actively maintained by the Jitsi team under 8×8, while community maintenance continues. Windows and macOS users are directed to GitHub releases, Debian and Ubuntu use a separately maintained APT repository, and the repository says no RPM packages are currently available.

For an existing installation, inventory the exact build and preserve rollback before changing it. For a new deployment, compare a currently maintained alternative and document why Jitsi Desktop remains necessary. Verify package provenance, signature or checksum where available, operating-system and Java-runtime support, vulnerability handling and an exit plan. A downloadable artifact is not a support commitment.

Keep release labels and package channels separate

The GitHub archive still marks Jitsi 2.8.5426 as Latest while the higher-numbered v2.11.5633 is marked Pre-release. The largest version number is therefore not automatically the stable deployment choice. The repository also separates Windows and macOS installers, the Debian or Ubuntu APT path and snapshot or pre-release channels. Preserve the channel, asset, retrieval date, operating system and runtime rather than reporting one universal current version.

Do not use historical release notes as a current compatibility matrix. A past fix for SIP, media, TLS or a platform-specific crash proves only that the referenced build changed. Re-run registration, calls, hold, transfer, DTMF, audio-device switching, reconnection and shutdown behavior on the exact retained package and operating system.

Bound SIP account and registrarless modes

The Windows setup guide associates SIP and XMPP links and the project supports SIP accounts. The registrarless guide describes direct peer use without a SIP registrar and warns that the mode is not intended for conversations over the public Internet. Registrarless calling, a PBX account and a public SIP service have different discovery, identity, NAT, authentication and emergency-service boundaries.

For a managed account, record registrar, outbound proxy, transport, credential owner, dial plan and revocation workflow. For an authorized direct-peer lab, constrain the network and peers and document the absence of provider routing. Do not expose a registrarless listener or infer PSTN, number, voicemail or emergency capability from a successful direct SIP call.

Revalidate protection, media and migration

Historical Jitsi Desktop material and release notes mention multiple protected-media and SIP behaviors, but the reviewed current repository does not define a modern supported TLS or SRTP profile, certificate-validation policy or interoperability promise. Inspect the actual signaling transport, trust result, SDP, negotiated media and failure behavior. A lock indicator, old feature list or encrypted one-to-one leg does not prove protection through a PBX or PSTN boundary.

Before retaining the client, test microphone and speaker selection, two-way audio, DTMF, hold and transfer if required, sleep and network recovery, logs, credential revocation and provider-approved emergency behavior. Build a migration record for accounts, contacts, call history and locally stored secrets without assuming every legacy data file can be safely imported. No installer, package signature, operating system, Java runtime, account, credential, registrar, PBX, NAT path, audio device, protected session, message, desktop share, emergency workflow or call was inspected or tested for this guide.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Hub · Primary softphone documentation reviewed through October 10, 2026; app, package, browser, mobile-wrapper, Windows audio and PBX interoperability not lab tested

Softphone research

Choose a desktop, mobile or browser calling client by SIP account, provisioning control, encryption and reliable call delivery.

Explore topic →
Guide · Primary desktop-softphone and operating-system documentation reviewed through October 10, 2026; app, audio-device and PBX interoperability not lab tested

Desktop softphones: SIP accounts and workstation operations

Evaluate installable clients on Windows, macOS and Linux with evidence for audio, registration, encryption and configuration ownership.

Read guide →
Client research · Current Linphone product, download, 6.2 release, stable desktop archives, third-party account, provisioning, push and security documentation rechecked October 7, 2026; the Windows, macOS and GNU/Linux stable archives all remained at desktop 6.2.3 dated September 22, 2026; no app, build, provisioning service, SIP account, Flexisip service, PBX, push, protected-media, message or call test

Linphone softphone: platform, provisioning and third-party SIP limits

Research the installable desktop and mobile clients, remote configuration and documented push boundary.

Read guide →
Client research · MicroSIP project, current-version pointer, stable downloads, help, troubleshooting and FAQ pages reviewed October 17, 2026. The current-version pointer and primary download table listed 3.22.19 for the regular and Lite editions with an October 3, 2026 release date. Package listing, installed build, active account, call authorization, negotiated signaling and media, Windows audio path and audible outcome remain separate evidence. No package, installation, Windows host, Wine environment, account, credential, PBX, provider, network, VPN, audio device, driver, SIP exchange, media stream, protected session, emergency workflow or live call was inspected or tested

MicroSIP: account mode, call path and protected-media boundaries

Keep the active SIP account, Local Account, dial plan, Call Manager, signaling address, media address and Windows audio path separate when deploying MicroSIP.

Read guide →
Protocol reference · RFC 3261 SIP, RFC 3711 SRTP, RFC 4568 SDP Security Descriptions, RFCs 5763 and 5764 DTLS-SRTP, and current Asterisk PJSIP documentation reviewed October 6, 2026; deployed endpoints, intermediaries, certificates and calls require direct verification

SIP TLS and SRTP: what each protects

Distinguish adjacent-hop signaling protection, SRTP media protection, SDES and DTLS-SRTP keying, and the actual termination points on every call leg.

Read guide →
Troubleshooting · RFC 3261 with current Asterisk PJSIP documentation; Asterisk 22 LTS and FreePBX 17 deployment context; no live test

SIP phone will not register: locate the failed evidence state

Separate local account state, REGISTER transport, endpoint identity, digest exchange, AoR binding and contact renewal.

Read guide →
Troubleshooting · Current Microsoft Windows audio-device and per-app routing guidance, Apple macOS input and output guidance and AVAudioSession route-change documentation, Android AudioManager reference, and W3C Media Capture and Audio Output specifications reviewed October 6, 2026; no computer, mobile device, dock, USB interface, Bluetooth device, browser, softphone, operating-system policy, PBX, media path or live call was inspected or tested

Softphone uses the wrong speaker, headset or microphone

Separate the connected device, operating-system defaults, per-app route, softphone selection, browser permission and active call path after docking, Bluetooth or USB changes.

Read guide →