Planet SIP

Jitsi: Changes coming to meet.jit.si

Fri, 09 Oct 2026 19:48:34 +0000

Starting today, meetings on meet.jit.si are limited to 95 minutes.

More changes are coming, stay tuned!

Your personal meetings team.

The post Changes coming to meet.jit.si appeared first on Jitsi.

Jitsi: Introducing Multi-screen support for Jitsi Meet

Thu, 01 Oct 2026 12:36:45 +0000

A Jitsi Meet participant has always been one browser window showing one layout. Put that meeting in a conference room with a display on every wall, or on a desk with two monitors, and the extra screens show the same thing the first one does, or nothing at all.

Multi-screen, built as a Google Summer of Code 2026 project, changes that. A single Jitsi Meet session can now render onto more than one display: the active speaker on one screen, a screenshare on another, the whiteboard on a third, without joining the conference twice.

One meeting, three surfaces: the meeting window, plus second screens showing the stage and the whiteboard. Composited from screenshots of each window.

Why not just open the room twice?

Plenty of room deployments do exactly that today. It works, but a second tab is a second participant: it shows up in the roster, it subscribes to and decodes its own copy of every stream, its audio has to be muted by hand, and nothing keeps the two windows in step.

A second screen is a rendering surface on top of the meeting you are already in. One connection to the bridge, one set of media subscriptions, no extra audio path. Nobody else in the meeting can tell it happened.

What a second screen can show

The stage, which follows the active speaker and honors pins
A tile grid of every participant
A screenshare, selectable by participant when several people are sharing
The whiteboard
A shared video, either YouTube or a direct link

Each of these is a role rather than a fixed stream. A window showing the stage re-points itself as people talk, and a tile grid updates as participants join and leave.

How it works

The interesting problem was rendering into a window the app does not own. A popup opened with window.open is a separate document, but a React portal will happily mount a component tree inside it. So a second screen is not a second app or a copy of anything: it is the same redux store and the same components, rendered through a portal into the popup.

Two things needed special handling:

Styling. Emotion injects CSS into the document it was created for, so each window gets its own style cache pointed at its own document head. Without it, the portal renders unstyled.
Media. Attaching the meeting window’s media stream to a video element in another window crosses a realm boundary, so each video clones the track and wraps the clone in the popup’s own constructor.

clone = track.clone();
video.srcObject = new win.MediaStream([ clone ]);

Cloning is cheap and adds no extra decode. It also gives the window a lifetime the feature controls: when the component unmounts, the clone stops.

Driving it from the iframe API

Multi-screen was built for room appliances: displays on the walls and no mouse in the room. So it is controlled through the iframe External API, with one command and three events. The API groundwork landed first, in #17527 by Emil Ivov, and the rendering layer was built on top of it.

// Put the active speaker on one display...
api.executeCommand('setSecondScreen', {
    id: 'wall-left',
    source: { role: 'stage' }
});

// ...and the screenshare on another.
api.executeCommand('setSecondScreen', {
    id: 'wall-right',
    source: { role: 'screenshare' },
    screen: 2
});

// Leaving out the source closes the window.
api.executeCommand('setSecondScreen', {
    id: 'wall-right'
});

The window ids belong to the embedder, so a room controller can address its displays by name and re-target them at any point. Three events report back:

secondScreenSourceChanged: what a window actually resolved to
secondScreenClosed: a window went away
secondScreenError: a window could not be opened, with one of six error codes

Driving it from inside the meeting

The command covers displays that were configured in advance. The more ordinary case is somebody in a normal meeting with a second monitor. For that, every place in the UI that shows something worth sending now offers to send it: participants get a Show on second screen entry in their context menu, and the screenshare and shared-video thumbnails get a button on hover. Clicking again takes it back.

The same action from three places: a participant’s context menu, the whiteboard tile, and a shared-video thumbnail.

A send never disturbs something you are already watching. It fills a free external display first, and only reuses a window once every display has one. The in-app triggers dispatch the same action as the API command, so an embedder listening to the events sees in-app activity too.

Good to know

Chromium only. Placing a window on a specific display needs the Window Management API, which today means Chromium-based browsers such as Chrome and Edge.
Two permissions. The site has to be allowed to open pop-ups and to manage windows. Without the second, the window still opens, but the browser decides where it lands.
The prompt needs a click. Chromium only shows the window-management prompt after a user gesture. The in-app triggers have one. An API command does not, so room appliances should grant the permission by policy.
Sources can come back. When a participant drops, their window waits a few seconds before closing, so a brief reconnect does not take the screen down with it.

Try it

Multi-screen is off by default. Deployments opt in through config:

secondScreen: {
    enabled: true
}

To try it without deploying anything, add #config.secondScreen.enabled=true to a room URL on beta.meet.jit.si, then open any participant’s context menu. The command, the events and the error codes are documented in the handbook.

The work

#17547: React portal rendering layer
#17581: stage, tile and gallery layouts, and the whiteboard as a source
#17598: gate the whiteboard second screen on whether the whiteboard is open
#17615: shared video as a second-screen source
#17666: in-app triggers
#17715: iframe API specs and a manual test checklist
handbook#683: API documentation

This work was done as part of Google Summer of Code 2026, mentored by Tudor Avram and Cosmin-Alexandru Timis. Thank you to both for the reviews, several of which changed a design rather than a line, and to the Jitsi community for a summer of work on something I get to keep using.

The post Introducing Multi-screen support for Jitsi Meet appeared first on Jitsi.

Digium: Cloud Phone System: A Practical Guide for Choosing the Best Fit

Tue, 29 Sep 2026 19:48:00 +0000

A cloud phone system carries your business calling on a provider’s servers and delivers it over your internet connection, with no PBX sitting in a closet. The best one for any given company is the system that matches four things: how many calls run at once, which sites cannot go quiet during an outage, the […]

The post Cloud Phone System: A Practical Guide for Choosing the Best Fit appeared first on Sangoma Technologies.

Digium: Vertical Markets Every VoIP Vendor and Reseller Should Target

Mon, 28 Sep 2026 20:49:00 +0000

A hotel, a dental clinic, and a metal fabrication plant might all sign for roughly the same number of lines, but they buy for different reasons, worry about different failures and bring different people into the decision. A generic UCaaS pitch has very little to hold onto in any of them. Once the conversation is […]

The post Vertical Markets Every VoIP Vendor and Reseller Should Target appeared first on Sangoma Technologies.

Digium: Chat AI vs. Voice AI: Which is Better for Your Business?

Mon, 28 Sep 2026 20:38:00 +0000

Chat AI and Voice AI are built on the same conversational engine, and each has a legitimate job. For the majority of companies, the smarter money goes to voice AI, because urgent problems still come in by phone, and a call that rings out costs a business far more than a chat window someone closed. […]

The post Chat AI vs. Voice AI: Which is Better for Your Business? appeared first on Sangoma Technologies.

Digium: How Can AI Call Transcription Improve Customer Service?

Fri, 18 Sep 2026 19:56:00 +0000

AI call transcription turns customer conversations into searchable text that businesses can review, analyze, and learn from. For customer service teams, it can make it easier to find recurring problems, understand how customers feel, review calls, and spot trends across hundreds or thousands of conversations. Your customers tell you what they need every day, and […]

The post How Can AI Call Transcription Improve Customer Service? appeared first on Sangoma Technologies.

Digium: How Do You Prepare Your Business Network for AI?

Tue, 15 Sep 2026 19:40:00 +0000

AI tools may live in the cloud, but their performance still depends on the network inside your business. If you plan to use AI meeting transcription, AI voice agents, real-time assistants, or other AI applications, your network needs enough bandwidth, low latency, reliable connectivity, strong security, and backup options to keep those tools working. Your […]

The post How Do You Prepare Your Business Network for AI? appeared first on Sangoma Technologies.

Jitsi: Introducing Document PiP for browser meetings

Wed, 02 Sep 2026 18:43:00 +0000

Jitsi already supported Video Picture-in-Picture in Electron, where PiP can open when focus moves away from the meeting window. The goal of this GSoC 2026 project was to bring interactive Document Picture-in-Picture to browser meetings, including automatic and manual entry.

The result supports standalone meetings and meetings embedded through the Jitsi IFrame API. Browsers with Document PiP support can display an interactive React interface with meeting controls. Where Document PiP is unavailable, Video PiP remains available on browsers that support it.

Automatic PiP behavior differs by platform. On supported Chromium based browsers, Document PiP can open automatically when the user switches to another tab. On WebKit based browsers, Video PiP opens when focus is lost from the meeting content. Users can also open PiP manually using the toolbar button. However, Electron app retains the existing Video PiP behavior.

Document PiP using React createPortal

For Chromium-based browsers, Jitsi registers the MediaSession enterpictureinpicture action handler. The browser can invoke this handler when the user switches away from the meeting tab. This behavior remains subject to the browser’s automatic-PiP permission and eligibility rules. Automatic Picture in Picture should be enabled for https://meet.jit.si/ site. A visibilitychange listener closes the Document PiP window when the user returns to the meeting tab.

For WebKit-based browsers, Jitsi uses Video PiP and the video element’s webkitSetPresentationMode() method to switch between picture-in-picture and inline. This implementation was inspired by the AutoPiP Safari extension.

In standalone meetings, React’s createPortal renders the PiP interface into the Document PiP window. The interface currently provides controls for muting or unmuting audio, enabling or disabling video, and leaving the meeting. These controls reuse existing Jitsi toolbar components and Redux actions.

The PiP window uses a compact layout that displays the current large-video participant. When the selected video is muted or unavailable, the participant’s avatar and display name are shown.

The iframe constraint

Embedded meetings face an additional limitation: the Document PiP specification allows requestWindow() only from a top-level browsing context. A meeting running inside an iframe therefore cannot open the Document PiP window directly. This restriction is tracked in an open WICG issue.

To resolve this, the meeting iframe sends an internal request through the existing IFrame API transport. The embedding page then opens and manages the Document PiP window using a per-API controller and loads a dedicated React renderer into it.

Because a conference MediaStreamTrack cannot be passed directly between cross-origin browsing contexts, the iframe forwards the selected video through a native RTCPeerConnection. Signaling uses internal External API transport messages and does not introduce a new public API. The embedded media bridge currently transports only the selected video track; conference audio continues to play from the original meeting iframe.

Merged work

Wrapping up

Jitsi Meet now supports an interactive Document PiP experience for standalone and embedded browser meetings, with Video PiP used as a fallback where supported. Users can keep the relevant participant visible, control their microphone and camera, and leave the meeting without returning to the main tab.

The feature becomes available when a deployment includes the merged changes and enables browser PiP using config pip.enableBrowserPiP.

The post Introducing Document PiP for browser meetings appeared first on Jitsi.

Digium: How to Choose an AI Phone System: A Buyer’s Guide

Tue, 01 Sep 2026 20:35:00 +0000

Picture a small chain of clinics where the phones at every site ring straight through the lunch hour, and by two o’clock nobody can say how many callers gave up and dialed a competitor. A missed call that becomes a lost patient is what sends most businesses looking at an AI phone system. An AI […]

The post How to Choose an AI Phone System: A Buyer’s Guide appeared first on Sangoma Technologies.

Digium: What Is AI Meeting Transcription and How Does It Work?

Thu, 27 Aug 2026 19:51:00 +0000

AI meeting transcription uses artificial intelligence to turn spoken conversations into written text automatically. Instead of taking notes during a video call or trying to remember what was said afterward, teams can create a written record of the conversation as it happens. For businesses with packed calendars, that changes the role of the meeting itself. […]

The post What Is AI Meeting Transcription and How Does It Work?Â appeared first on Sangoma Technologies.

WebRTC Hacks: Comparing WebRTC video codecs with a proper dataset

Thu, 27 Aug 2026 11:39:17 +0000

Stumbling over Microsoft’s Video Conferencing Dataset (VCD) I asked Claude to take on a video codec engineer’s favorite hot take: compare video codecs. It did a fairly good writeup using the tooling provided by libWebRTC. One of the most surprising results was that background blur makes H.264 a lot more effective. Other than that, the […]

The post Comparing WebRTC video codecs with a proper dataset appeared first on webrtcHacks.

Jitsi: Tracing calls through backend components

Thu, 20 Aug 2026 10:26:25 +0000

The goal of the project was to implement distributed tracing across the main backend components of Jitsi. In short, distributed tracing is a technique for tracing requests across distributed components by generating events in each component and stitching them together using identifiers. The idea was not to fully integrate distributed tracing into the whole system but to have end-to-end traces for common flows that can be used as a base for future tracing.

The following flows are now traced:

Creating a conference
Joining a conference, which also includes inviting JVB
Leaving or ending a conference
Inviting a Jibri recorder

For example, when a client joins a conference, it first joins the MUC room, then Prosody notifies Jicofo, who allocates a bridge and initiates a jingle session. Tracing this involved injecting code in the Meet client, Prosody, Jicofo, and JVB. The trace looks like this:

There were two main challenges while implementing this. The first challenge was understanding the whole system. What does each component do? How does it interact with the other components? When does it do so? As the amount of code required for this to work was small, the difficult part was actually finding exactly where to put it.

The second challenge was finding a way of propagating context. It was not enough to record the main steps of each component, but we also needed a way to stitch them together. As all communication is done through Prosody, I implemented an XMPP extension inspired by the W3C standard: https://github.com/jitsi/jitsi-xmpp-extensions/pull/146.

To enable tracing, we need a tracing backend (Tempo), an OpenTelemetry collector (Alloy), and a frontend (Grafana). An example of how to set everything up can be found in docker-jitsi-meet: https://github.com/jitsi/docker-jitsi-meet/pull/2303.

For next steps, this should be enabled in production to start gathering real data and understand which information is more valuable. There are also many other flows that could be traced but fall outside the scope of this project: inviting a transcriber, inviting SIP participants (Jigasi), changes in room metadata, etc.

Below is a list of all the PRs that were developed as part of the project.

The post Tracing calls through backend components appeared first on Jitsi.

Digium: Best Office Phone System: How to Choose for One Office, Remote Teams, or Multiple Locations

Mon, 10 Aug 2026 20:20:17 +0000

Choosing the best office phone system comes down to one variable: how your team is physically arranged. Three patterns cover nearly every business. When everyone works from a single address, the platform barely matters, because most current unified communications systems handle that case well. Scatter those same people across home offices and the priorities invert, […]

The post Best Office Phone System: How to Choose for One Office, Remote Teams, or Multiple Locations appeared first on Sangoma Technologies.

Digium: Does Your Business Need a Better Network for AI? Here’s How to Tell

Wed, 05 Aug 2026 18:25:58 +0000

If you’re planning to use AI, your network for AI is just as important as the software itself. Every AI application depends on moving data quickly, securely, and reliably between people, devices, cloud services, and business systems. If the network struggles to keep up, AI becomes slower, less reliable, and harder for employees to trust. […]

The post Does Your Business Need a Better Network for AI? Here’s How to Tell appeared first on Sangoma Technologies.

Digium: UC Integration: How It Works

Tue, 04 Aug 2026 19:53:04 +0000

Many teams run voice in one app, video in another, chat in a third, and their CRM somewhere else. Every handoff between those systems costs a few seconds of copying a number, hunting for a record, or switching windows, and those seconds add up across a day of calls. UC integration connects a unified communications […]

The post UC Integration: How It Works appeared first on Sangoma Technologies.

Digium: Business Phone System With 24/7 Support: How to Keep Calls Running Around the Clock

Wed, 29 Jul 2026 20:42:50 +0000

A business phone system with 24/7 support pairs an architecture that keeps calls connected around the clock, including during internet or power outages, with a support team a business can reach at any hour when something goes wrong. The deployment architecture decides whether calls stay connected, and the vendor’s support model decides whether someone answers […]

The post Business Phone System With 24/7 Support: How to Keep Calls Running Around the Clock appeared first on Sangoma Technologies.

Digium: Business Phone System With 24/7 Support: How to Keep Calls Running Around the Clock

Wed, 29 Jul 2026 18:28:01 +0000

The post Business Phone System With 24/7 Support: How to Keep Calls Running Around the Clock appeared first on Sangoma Technologies.

Jitsi: A new architecture for transcription (and more)

Tue, 14 Jul 2026 15:32:39 +0000

Back in 2017 we shipped a speech-to-text prototype for Jitsi Meet. It was built on Jigasi, and for the better part of a decade that is how transcription in Jitsi worked. It served us well — but it also accumulated a fair amount of technical debt. We now have a new architecture that replaces Jigasi for transcription: it is simpler to run, cheaper to operate, works with a range of speech-to-text providers, and it is cloud-native.

Why replace Jigasi?

Jigasi started life as a SIP gateway — its job was to bridge regular telephony into a conference. Transcription was bolted on later: to transcribe a meeting, a Jigasi instance joins the conference as a hidden participant, receives everyone’s audio, and relays it to a speech-to-text service.

That works, but it carries a lot of baggage. Jigasi is a full XMPP client with a SIP stack attached. Every transcribed conference ties up a stateful Jigasi that has to join the MUC, and audio has to be routed out of the bridge, into Jigasi, and back again. Scaling it means running and load-balancing a fleet of Jigasi instances. That is a lot of moving parts for what is, fundamentally, “send some audio to an API and get text back.”

The new architecture

The key observation is that the media already flows through the Jitsi Videobridge (JVB). So instead of pulling audio back out into a separate component, we let the bridge send it straight to a transcription service.

Jicofo decides when a conference should be transcribed and tells the bridge which service URL to connect to. The bridge opens a single WebSocket to the transcription service and forwards each participant’s Opus audio, tagged per source. The service decodes the audio, streams it to a speech-to-text backend, and streams the results back over the same connection, where they are turned into the captions users see. Jicofo also passes along any HTTP headers, so the service can sit behind an authenticating proxy such as Cloudflare Access.

That is the whole design. There is no extra conference participant, and no second media path — and with it goes an entire class of operational complexity.

A simple protocol on the wire

The bridge and the service talk over a plain JSON-over-WebSocket protocol. We did not invent it from scratch — it is based on VoxImplant’s WebSocket audio-streaming format, in which audio travels as base64 inside a `media` event. Reusing an existing format kept the service compatible with other audio producers (it happily accepts ogg-opus from VoxImplant, for example) and gave the bridge, through a small jicoco-mediajson library, a well-understood thing to implement.

We then extended it with the few events we actually needed: “ping”/”pong” for keepalive, an “info” event so each side can announce itself (application, version, active provider), a per-source “start”, and a “transcription-result” envelope that carries the text back.

A frame of audio going from the bridge to the service looks like this:

{ “event”: “media”,
“media”: { “tag”: “participant-7”, “chunk”: 42, “timestamp”: 1751979219, “payload”: “[base64 Opus]” } }

and a result coming back:

{ “event”: “transcription-result”, “type”: “transcription-result”,
“participant”: { “id”: “participant-7” }, “language”: “en”, “is_interim”: false,
“transcript”: [ { “text”: “hello world”, “confidence”: 0.98 } ] }

A handful of event types is all it takes to move audio in and text — or translated audio — back out.

Pluggable backends

The service itself — opus-transcriber-proxy — is a thin proxy in front of the actual speech-to-text engine. Out of the box it supports xAI, OpenAI’s realtime transcription, Deepgram, and Google Gemini, with a configurable priority order and automatic failover between them. It also speaks to any OpenAI-compatible endpoint, so you can point it at a model you host yourself — no audio has to ever leave your own infrastructure.

…and more

Because the bridge now speaks a simple “audio in, media out” protocol to the service, transcription is only the first thing we can build on it. The same pipeline drives real-time speech-to-speech translation, a feature we’re currently working on where a speaker’s audio is translated, re-encoded as Opus, and played back into the conference in the target language, alongside translated captions. Same architecture, different endpoint.

And there is plenty more the same foundation makes possible — multitrack audio recording straight off the bridge, or connecting a conference directly to an AI agent that can listen and talk back in real time. Anything that wants access to a meeting’s audio no longer needs a Jigasi and a hidden participant; it just needs to speak this protocol.

Docker or Cloudflare, natively

The service runs anywhere. You can run it as a plain Docker container alongside the rest of your deployment, or you can deploy it natively to Cloudflare — it ships as a Cloudflare Container fronted by a Worker, with request routing and container pooling built in, so you can run transcription at the edge without managing any servers of your own.

Try it

Getting started is essentially a `docker run` away:

docker run -d -p 9090:8080 \
-e PROVIDERS_PRIORITY=openai \
-e OPENAI_API_KEY= \
jitsi/opus-transcriber-proxy:latest

Point Jicofo at it, enable transcription in Prosody and `config.js`, and you are transcribing. The full setup — Docker and Cloudflare, the Prosody and Jicofo configuration, and Cloudflare Zero Trust — is documented in the handbook.

This is as much a foundation as it is a feature. Retiring Jigasi for transcription clears a big chunk of technical debt and gives us a clean, pluggable, cloud-native path for real-time AI on top of Jitsi audio — starting with transcription and translation, with more to come. Jigasi-based transcription is now deprecated and will be removed in a future release, so if you are self-hosting, this is a good time to migrate.

The post A new architecture for transcription (and more) appeared first on Jitsi.

Digium: Unified Communications for Enterprise: What to Know Before You Commit

Mon, 13 Jul 2026 19:55:01 +0000

Enterprise communications rarely arrive by design. They accumulate. A few buildings still run legacy PBXs, one region signed a different carrier, and separate cloud calling and video tools spread through individual teams. Acquisitions, regional requirements, and years of independent decisions leave large organizations with a communication estate that is costly to run, inconsistent across locations, […]

The post Unified Communications for Enterprise: What to Know Before You Commit appeared first on Sangoma Technologies.

Digium: Unified Communications for Enterprise: What to Know Before You Commit

Mon, 13 Jul 2026 19:44:00 +0000

The post Unified Communications for Enterprise: What to Know Before You Commit appeared first on Sangoma Technologies.

Jitsi: Google Summer of Code 2026 – Meet This Year’s Projects!!

Wed, 08 Jul 2026 16:23:51 +0000

Another summer, another exciting cohort of contributors joining the Jitsi community! We’re thrilled to announce the five projects underway for Google Summer of Code 2026. Each one tackles a meaningful part of the Jitsi stack, and each one is being driven by a student contributor stepping into open source — many for the very first time.

For years, Jitsi has been a home for newcomers to open source. Our maintainers remember what it’s like to submit that nervous first pull request, and we’ve built our GSoC program around that spirit: real mentorship, real code that ships to millions of users, and a welcoming community that meets first-timers where they are. GSoC has always been more than a summer internship for us — it’s how we grow the next generation of contributors, and many of our past students have gone on to become long-term maintainers and mentors themselves.

Here’s what our 2026 contributors are building.

The 2026 Projects

Chat Moderation & Editing

Jitsi’s chat is getting a serious upgrade. This project adds the moderation and editing tools that today’s chat is missing — giving moderators the ability to delete and redact messages, mute or remove participants, and handle user reports directly from the chat interface. Users will also be able to edit their own messages with version history and search through chat history more easily. It’s a substantial improvement to everyday usability for anyone running a meeting.

JavaScriptReactReact NativeProsody

Contributor: Alok Raj

Mentors: Mihaela Dumitru, Calin Chitu

Tracing Calls Through Backend Components

Debugging a distributed system is hard when you can’t follow a single call through it. This project brings distributed tracing (using modern observability tooling like OpenTelemetry) to Jitsi’s backend, correlating traces across JVB, Jicofo, and Prosody so developers and operators can see exactly how a call moves through the stack. The result is better debugging, clearer performance analysis, and sample dashboards for common scenarios.

JavaKotlinLuaOpenTelemetryDistributed SystemsObservability

Contributor: Julián González Calderón

Mentors: Aaron van Meerten, Scott Boone

Rewrite Jibri to Use the iframe API

Jibri, our recording and live-streaming component, currently loads Jitsi Meet directly in a headless browser. This project rewrites it to use the External (iframe) API instead — a cleaner architecture that means better control over the meeting, easier maintainability, and access to new API features for enhanced recording, all while keeping full parity with today’s capabilities.

KotlinJavaSelenium WebDriverJavaScript

Contributor: Hugo Lavernhe

Mentors: Damyan Minkov, Jaya Allamsetty

Document Picture-in-Picture for Browser Meetings

Modern browsers now support the Document Picture-in-Picture API, which lets an entire interactive document (not just a video) float in an always-on-top window. This project brings that to Jitsi Meet, so you can keep your meeting visible and interactive while working in other apps — complete with customizable layouts and in-window controls for mute, video, and chat.

JavaScriptTypeScriptReactDocument PiP APICSS

Contributor: Bandhan Majumder

Mentors: Hristo Terezov, Horatiu Muresan

Multi-Screen Support

Today, one participant means one window and one layout. This project changes that by distributing a single meeting session across multiple windows and displays. Imagine the active speaker on one screen, gallery view on another, and different participant groups on their own displays — all kept in sync. It’s a big step forward for power users, event setups, and anyone with room to spread out.

JavaScriptTypeScriptReactWebRTC

Contributor: Abhay Madan

Mentors: Tudor Avram, Cosmin-Alexandru Timis

To Our Contributors and Community

To our 2026 students: welcome. You’re joining a project used by people all over the world, and the work you do this summer will be part of that.

And to everyone considering their first open source contribution someday — whether through GSoC or otherwise — Jitsi’s doors are open. That first pull request is closer than you think.

Happy hacking, and here’s to a great summer!

The post Google Summer of Code 2026 – Meet This Year’s Projects!! appeared first on Jitsi.

Digium: Unified Communications for Startups: How to Set Up Comms That Scale With You

Thu, 02 Jul 2026 18:54:29 +0000

The communication setup that carries a startup to its first ten people is usually a collection of free or personal tools: founders’ mobile numbers, a chat app, a separate video tool, and a texting app that has nothing to do with the business line. It works at that size. The strain shows around 30 people, […]

The post Unified Communications for Startups: How to Set Up Comms That Scale With You appeared first on Sangoma Technologies.

Digium: Unified Communications for Startups: How to Set Up Comms That Scale With You

Thu, 02 Jul 2026 18:54:00 +0000

The post Unified Communications for Startups: How to Set Up Comms That Scale With You appeared first on Sangoma Technologies.

WebRTC Hacks: Vector Vibing to speed up Opus encode by 20%

Thu, 02 Jul 2026 12:34:00 +0000

tl;dr: Opus encoding just got 20% faster on desktop Chromium by turning on AVX2 vectorization in libopus. Vectorization means one instruction doing the same arithmetic on a whole vector of values at once instead of one at a time. Codecs spend their hot loops running identical math across long buffers of samples, exactly where vectorization […]

The post Vector Vibing to speed up Opus encode by 20% appeared first on webrtcHacks.

Digium: What Should You Look for in a Single-Vendor Communications Provider in 2026? A Buyers Guide

Tue, 30 Jun 2026 18:47:16 +0000

The biggest thing to look for in a single-vendor communications provider is whether they actually own their voice infrastructure or just resell someone else’s. Vendor consolidation lowers your costs, cuts downtime, and shrinks the number of places things can break, as long as your provider controls the technology end to end instead of stitching together […]

The post What Should You Look for in a Single-Vendor Communications Provider in 2026? A Buyers Guide appeared first on Sangoma Technologies.

Digium: What Should You Look for in a Single-Vendor Communications Provider in 2026? A Buyers Guide

Tue, 30 Jun 2026 18:47:00 +0000

The post What Should You Look for in a Single-Vendor Communications Provider in 2026? A Buyers Guide appeared first on Sangoma Technologies.

Digium: A Small Business Guide to Unified Communications

Fri, 26 Jun 2026 16:56:00 +0000

When a small business misses a call, it risks losing the customer, and some won’t call back, they just call the next business on the list. And it misses more of them than it should, because the few people who answer the phone are the same people doing everything else: already on another line, out […]

The post A Small Business Guide to Unified Communications appeared first on Sangoma Technologies.

Digium: A Small Business Guide to Unified Communications

Fri, 26 Jun 2026 16:50:08 +0000

The post A Small Business Guide to Unified Communications appeared first on Sangoma Technologies.

Digium: How to Scale a Business Phone System from One Location to Twenty (Without Starting Over Each Time)

Wed, 24 Jun 2026 19:31:07 +0000

The short answer: The best way to scale a business phone system across multiple locations is to choose a platform built for it from the start, one that lets you replicate the same setup at each new site without rebuilding from scratch or adding new vendors. If you are managing two locations now and planning […]

The post How to Scale a Business Phone System from One Location to Twenty (Without Starting Over Each Time)Â appeared first on Sangoma Technologies.

Digium: How to Scale a Business Phone System from One Location to Twenty (Without Starting Over Each Time)

Wed, 24 Jun 2026 19:31:00 +0000

The post How to Scale a Business Phone System from One Location to Twenty (Without Starting Over Each Time)Â appeared first on Sangoma Technologies.

Digium: Sangoma vs 3CX: Which Business Phone System Fits Your Needs?

Thu, 18 Jun 2026 20:45:43 +0000

When a business starts shopping for a phone system replacement, Sangoma and 3CX tend to land on the same shortlist. Both serve businesses replacing aging phone systems. Both handle voice, video, and messaging. Both show up in the same search results. On a feature checklist, they look like close competitors. They aren’t. The two platforms […]

The post Sangoma vs 3CX: Which Business Phone System Fits Your Needs? appeared first on Sangoma Technologies.

Digium: How Schools Improve Emergency Communication and Daily Operations with One System

Thu, 18 Jun 2026 20:44:39 +0000

Most school districts run communication on a mix of systems. The phone system is from one vendor. The PA system is from another. Emergency alerts come from a third. Digital signage, intercoms, and bells all have their own platforms, their own support contacts, and their own renewal cycles. When everything is working, it’s manageable. When […]

The post How Schools Improve Emergency Communication and Daily Operations with One SystemÂ appeared first on Sangoma Technologies.

Digium: Why Selling UCaaS Alone Can Limit Your Growth (And What to Do Instead)

Thu, 18 Jun 2026 20:43:21 +0000

If you sell UCaaS and only UCaaS, you are leaving money on the table. That is not a knock on cloud phone systems. Business phone systems are a strong product. Customers need them. They buy them. But if that is the only thing you sell, you are competing on price, fighting for attention, and starting […]

The post Why Selling UCaaS Alone Can Limit Your Growth (And What to Do Instead) appeared first on Sangoma Technologies.

Digium: How to Build a Profitable Communications Portfolio Without Adding Complexity

Thu, 18 Jun 2026 20:41:02 +0000

If you’ve been in the channel long enough, you’ve probably been here: a customer calls with a problem, and you spend the first 20 minutes figuring out which vendor owns it. Then you spend the next hour on hold with that vendor, who blames a different vendor. Meanwhile, your customer is down, and you’re the […]

The post How to Build a Profitable Communications Portfolio Without Adding ComplexityÂ appeared first on Sangoma Technologies.

Digium: How to Build a Profitable Communications Portfolio Without Adding Complexity

Thu, 18 Jun 2026 18:34:16 +0000

The post How to Build a Profitable Communications Portfolio Without Adding ComplexityÂ appeared first on Sangoma Technologies.

Digium: Why Selling UCaaS Alone Can Limit Your Growth (And What to Do Instead)

Wed, 17 Jun 2026 19:59:26 +0000

The post Why Selling UCaaS Alone Can Limit Your Growth (And What to Do Instead) appeared first on Sangoma Technologies.

Digium: Sangoma vs Dialpad: Choosing the Right Business Communications Provider

Fri, 12 Jun 2026 20:44:53 +0000

Dialpad leads with AI-powered collaboration for cloud-native teams. Sangoma covers cloud, hybrid, and on-premises deployment with full ownership of the stack underneath it. The right pick depends on which of those two things your operations actually need more. Why Compare Sangoma and Dialpad? Dialpad and Sangoma both show up on cloud phone shortlists, but they […]

The post Sangoma vs Dialpad: Choosing the Right Business Communications Provider appeared first on Sangoma Technologies.

Digium: How Schools Improve Emergency Communication and Daily Operations with One System

Fri, 12 Jun 2026 20:17:41 +0000

The post How Schools Improve Emergency Communication and Daily Operations with One SystemÂ appeared first on Sangoma Technologies.

Digium: Sangoma vs 3CX: Which Business Phone System Fits Your Needs?

Thu, 11 Jun 2026 20:30:22 +0000

The post Sangoma vs 3CX: Which Business Phone System Fits Your Needs? appeared first on Sangoma Technologies.

Digium: One Provider vs Multiple Vendors: Which Model Holds Up Under Pressure?

Mon, 08 Jun 2026 19:45:24 +0000

Picture this: your phones go down on a Monday morning. Your contact center platform stops routing calls. Your managed network service provider says the issue is on the UCaaS side. Your UCaaS vendor says it looks like a network problem. Meanwhile, your team is losing sales, missing support calls, and explaining outages to your own […]

The post One Provider vs Multiple Vendors: Which Model Holds Up Under Pressure?Â appeared first on Sangoma Technologies.

Digium: How Partners Grow Faster by Selling Integrated Solutions

Fri, 05 Jun 2026 20:00:23 +0000

Most partners start a customer conversation with one product. A business phone system with on-premises or hybrid deployment options. A SIP trunk. Maybe a contact center platform. They close the deal, collect the commission, and move on. That model works. It just leaves a lot of money on the table. Partners who sell across the […]

The post How Partners Grow Faster by Selling Integrated SolutionsÂ appeared first on Sangoma Technologies.

WebRTC Hacks: Vibe-coding WebRTC

Tue, 02 Jun 2026 11:08:06 +0000

Well, that title is clickbait for Hacker News. The honest title would have been “using AI to tackle long-standing WebRTC issues.” Posts on webrtcHacks are rare these days, and in German we would say there are Unkenrufe that WebRTC is dead. It is not. It is the infrastructure for meetings, game streaming, and voice AI, […]

The post Vibe-coding WebRTC appeared first on webrtcHacks.

Digium: Microsoft Teams Integration With Sangoma: How It Works and the Benefits

Tue, 02 Jun 2026 00:15:00 +0000

Microsoft Teams has become the default workspace for millions of businesses. Meetings, messaging, file sharing: it handles the collaboration layer well. But when it comes to business-grade voice calling, Teams alone often leaves gaps that matter: limited call routing, inconsistent reliability, and licensing costs that can creep up as your organization grows. Sangoma’s Microsoft Teams […]

The post Microsoft Teams Integration With Sangoma: How It Works and the Benefits appeared first on Sangoma Technologies.

Digium: Microsoft Teams Integration With Sangoma: How It Works and the Benefits

Mon, 01 Jun 2026 21:30:11 +0000

The post Microsoft Teams Integration With Sangoma: How It Works and the Benefits appeared first on Sangoma Technologies.

Digium: Sangoma vs RingCentral: Full Comparison for an Informed Decision

Mon, 01 Jun 2026 21:12:51 +0000

Both Sangoma and RingCentral are established UCaaS providers, but they are built on different philosophies around deployment, pricing, and support. This comparison helps SMB buyers compare deployment options, core capabilities, pricing, and support. It does not cover custom enterprise quotes or plan-specific exceptions. Why Are We Comparing Sangoma and RingCentral? RingCentral appears on almost every UCaaS […]

The post Sangoma vs RingCentral: Full Comparison for an Informed Decision appeared first on Sangoma Technologies.

Digium: Sangoma vs RingCentral: Full Comparison for an Informed Decision

Mon, 01 Jun 2026 18:01:53 +0000

The post Sangoma vs RingCentral: Full Comparison for an Informed Decision appeared first on Sangoma Technologies.

Digium: What Is STIR/SHAKEN and Why It Matters for Your Business

Thu, 21 May 2026 20:13:52 +0000

STIR/SHAKEN is a call authentication framework, required by the FCC, that digitally signs outbound calls so receiving networks can verify the caller ID hasnâ€™t been faked. STIR stands for Secure Telephony Identity Revisited; SHAKEN stands for Signature-Based Handling of Asserted information using toKENs. The two work together as a technical standard and governance framework for […]

The post What Is STIR/SHAKEN and Why It Matters for Your Business appeared first on Sangoma Technologies.

Digium: Why Voice Is Becoming Important Again in the Era of AI Agents

Thu, 21 May 2026 17:57:00 +0000

For the past decade or so, the Unified Communications (UC) industry has been focused on improving how people connect. Vendors competed on calling features, collaboration experiences, messaging capabilities, mobility, and video conferencing. The goal was straightforward: make communication faster, easier, and more accessible from anywhere. Now, a new shift is emerging across the communications industry, […]

The post Why Voice Is Becoming Important Again in the Era of AI Agents appeared first on Sangoma Technologies.

Digium: What Is STIR/SHAKEN and Why It Matters for Your Business

Wed, 20 May 2026 21:17:00 +0000

The post What Is STIR/SHAKEN and Why It Matters for Your Business appeared first on Sangoma Technologies.

Digium: Why Voice Is Becoming Important Again in the Era of AI Agents

Wed, 20 May 2026 17:07:31 +0000

The post Why Voice Is Becoming Important Again in the Era of AI Agents appeared first on Sangoma Technologies.

Digium: Why Healthcare IT Teams Are Consolidating Communications and Network Providers

Mon, 18 May 2026 21:00:23 +0000

Healthcare IT teams are under constant pressure. Staff need to reach each other instantly. Patients expect fast, clear communication. Regulators want airtight security. Leadership wants costs down, and they want them down now. For a long time, the answer was to add more vendors. One for phone systems. Another for network connectivity. A third for […]

The post Why Healthcare IT Teams Are Consolidating Communications and Network ProvidersÂ appeared first on Sangoma Technologies.

Digium: Why Healthcare IT Teams Are Consolidating Communications and Network Providers

Mon, 18 May 2026 20:20:39 +0000

The post Why Healthcare IT Teams Are Consolidating Communications and Network ProvidersÂ appeared first on Sangoma Technologies.

Digium: How Integrated Communications Improve Reliability Across Multi-Location Businesses

Thu, 14 May 2026 21:20:55 +0000

Your customer has 20 locations. A branch in Denver loses voice calls for three hours on a Tuesday morning. By the time your customer’s IT team figures out whether the problem is the cloud calling platform, the SD-WAN, the internet circuit, or the firewall config, the damage is done. Customers couldn’t get through. Employees worked […]

The post How Integrated Communications Improve Reliability Across Multi-Location BusinessesÂ appeared first on Sangoma Technologies.

Digium: How Integrated Communications Improve Reliability Across Multi-Location Businesses

Thu, 14 May 2026 21:03:54 +0000

The post How Integrated Communications Improve Reliability Across Multi-Location BusinessesÂ appeared first on Sangoma Technologies.

Digium: The Business Case for One Vendor: Cost, Control, and Accountability

Thu, 07 May 2026 21:38:36 +0000

When something breaks in a multi-vendor environment, the first thing that happens isn’t a fix. It’s a phone call. Then another. Then an email chain where Vendor A blames Vendor B, and your customer is stuck in the middle waiting for someone to own the problem. That’s the real cost of vendor sprawl, and it […]

The post The Business Case for One Vendor: Cost, Control, and AccountabilityÂ appeared first on Sangoma Technologies.

Digium: The Business Case for One Vendor: Cost, Control, and Accountability

Thu, 07 May 2026 21:20:42 +0000

The post The Business Case for One Vendor: Cost, Control, and AccountabilityÂ appeared first on Sangoma Technologies.

Digium: What Is a Cloud Contact Center? A Complete Guide

Thu, 07 May 2026 20:49:48 +0000

The contact center is the most customer-facing part of any business and, somehow, reliably the last to get modernized. The accounting software moved to the cloud years ago. Email, file storage, video calls, all cloud. But the system that actually handles your customers calling in with a problem? That one’s still running on hardware someone […]

The post What Is a Cloud Contact Center? A Complete Guide appeared first on Sangoma Technologies.

Digium: What Is a Cloud Contact Center? A Complete Guide

Thu, 07 May 2026 16:42:16 +0000

The post What Is a Cloud Contact Center? A Complete Guide appeared first on Sangoma Technologies.

Digium: Telecom Compliance Is Not About Avoiding Fines Anymore.

Fri, 01 May 2026 18:32:26 +0000

There is a quiet shift happening in telecom right now, and most providers (ITSPs, CSPs and MSPs) have not adjusted to it. Compliance is still widely treated as a regulatory obligation, something to revisit when rules change, or audits require it. However, that framing no longer reflects reality. Today, compliance plays a direct role in whether communications actually work. […]

The post Telecom Compliance Is Not About Avoiding Fines Anymore. appeared first on Sangoma Technologies.

Digium: Hybrid UCaaS Implementation: The Deployment Guide

Wed, 29 Apr 2026 18:19:47 +0000

Deploying hybrid UCaaS is more involved than spinning up a pure cloud system. There’s an on-site appliance to install, failover paths to configure, and a cloud layer that needs to sync with local infrastructure before anything goes live. Most of that complexity sits on Sangoma’s side of the table â€” but understanding what happens at […]

The post Hybrid UCaaS Implementation: The Deployment Guide appeared first on Sangoma Technologies.