Voice Disconnects When You Teleport.
complete
Eagle Himmel
I am in a private call. I teleport away from the region where I am speaking to a friend. I have voice for maybe 10-30 seconds in the new region, then it fails. In the chat box it says "[5:44 AM] Second Life: Lycan Drascol started a voice call
[5:44 AM] Second Life: Lycan Drascol started a voice call" over and over until you hit the call button to stop it. Then you cannot reconnect to voice. I teleport back to the region I started at but I still cannot connect to voice either in local or private unless 1 or both of us relog. It does not appear to matter where I teleport to, the outcome is the same. Unless my friend comes with me, then we can stay connected.
Log In
Maestro Linden
updated the status to
complete
The fix for this issue has been deployed grid-wide with this server update: https://releasenotes.secondlife.com/simulator/2026-05-12.25766421211.html
Maestro Linden
Hubbel Heron Eagle Himmel in case either of you are interested in testing the server version with this fix, the "Second Life Preflight" and "Second Life RC BlueSteel" channels currently have it, with version 2026-05-01.25230815207. The 'WebRTC Voice [1-4]' regions are on this version, as well as (most of?) the Blake Sea regions. Note that in order to enjoy the fix, you'll want to be sure that both regions are on that newer version.
Maestro Linden
Merged in a post:
WebRTC Voice Chat
Hubbel Heron
WebRTC Voice Chat Outage
Hubbel Heron
In my opinion, there are massive problems with the new “Secondlife WebRTC Gateway.”
Private or IM voice is almost impossible.
The only place that works is in my SL home. If we (my partner and I) switch to another (any) region, the voice connection is interrupted and only a public connection is possible, unless voice is deactivated there.
Are we alone in the wide corridor with these experiences, or are there reports from other people affected?
We use “Firestorm version 7.2.3 (80036)
It is perhaps worth mentioning that there were no such problems with the Vivox version.
Greetings
Hubbel Heron
My PC configuration: Windows 11 Home up to date.
Device name DESKTOP-EBGDUCV
Processor Intel (R) Core (TM) i9-10900KF CPU @ 3.70GHz (3.60 GHz)
Installed RAM 64.0 GB
NVIDIA GeForce RTX 3080 10GB graphics card
253 GB of 932 GB storage used
System type 64-bit operating system, x64-based processor
Hecklezz Resident
Hubbel Heron Our latest Firestorm 7.2.4 beta that went out yesterday has all of the latest WebRTC viewer fixes that have came out from LL since our 7.2.3 release back in February. If you want the best experience using WebRTC voice, we highly recommend users of LL's viewer to use their 26.2, and users of Firestorm to use our 7.2.4 beta.
The voice disconnecting when changing region issue as mentioned by Maestro is being fixed server-side and the beta won't help with that, but a lot of other issues you may have are possibly already fixed.
LL's Second Life Viewer 26.2-
Firestorm 7.2.4 beta-
Maestro Linden
updated the status to
tracked
Maestro Linden
Hi Eagle Himmel thanks for the report. The fix for this issue (referred to internally as server#2514) is currently making its way through the RC channels: https://releasenotes.secondlife.com/simulator/2026-05-01.25230815207.html
Wesley Huntsman
Maestro LindenHas the fix been applied yet because the issue is still persisting?
Maestro Linden
Wesley Huntsman: It's only fixed in the server versions newer than 2026-05-01.25230815207. The server with the fix for this bug (newest is 2026-05-12.25767303752) is currently only deployed to a portion of the grid (~25%), though it should go to the rest of the grid tomorrow (May 19). If both users are on a region using the newer server build, it should be fixed, but not if they're on regions running 2026-03-04.22660319648.
Eagle Himmel
Maestro Linden Today I lost voice again while I was on mainland and my friend went to a premium sandbox. In order to reconnect to voice we had to re-log.
Maestro Linden
Eagle Himmel: Can you elaborate on that failure?
Were you on a p2p call with your friend when they teleported? If so, do you know what the timing was between them teleporting and the call being dropped? When you say that you 'lost voice', were you unable to connect to spatial voice chat (no voice dot)?
Finally, is the failure reliable or did it appear to fail once out of many teleport or crossing events?
Eagle Himmel
Maestro Linden: Yes, we often chat privately incase visitors pop in. So here's what happens. 1. We open a private call. 2. I teleport to a different sim. 3. 20-45 seconds go by and we can no longer chat. 4. I try to open a private chat and get these messages that don't ever stop even if you close chat.
"[2026/05/25 5:28 AM] Second Life: Lycan Drascol started a voice call
[2026/05/25 5:28 AM] Second Life: Lycan Drascol started a voice call
[2026/05/25 5:28 AM] Second Life: Lycan Drascol started a voice call"
If I re-log and Lycan does not, you can start a call, but the other cannot hear. Or your message that you are waiting for them to pick up never goes away even though they did answer.
One thing I have not yet tried was to open a private call after teleporting. I'll experiment next time and see if there is a difference.
Maestro Linden
Eagle Himmel: Okay, thanks for the clarification and details about the steps to reproduce the issue.
The original bug about p2p calls being dropped 100% of the time after TP or region crossing (server#2514 internally) _should_ be fixed with server 2026-05-12.25766421211. There's an open issue about calls being dropped about 20% the time when one of the parties region crosses very aggressively (several times a minute), while on a call, though your case doesn't seem to meet those criteria.
I'm not able to reproduce the call drop on a basic TP/crossing any more, so we need more details from you (or others who can reproduce it) to investigate further.
Some basic details I'd to know are:
- Is the call drop happening 100% of the time, or just sometimes?
- Which viewer versions are both of you on? Are you both on Second Life Release 26.2, or some other version? Note that for Firestorm users, the latest 7.2.4 beta viewer should be up to date with the latest voice bug fixes found in 26.2, but that 7.2.3 has several known bugs around voice.
- Could you capture the details of a specific dropped call incident? The details we could use are:
- A basic timeline of the events around the call
- A viewer log file from the event. In this case, I think the log file from the viewer that teleported would be the one we want.
To send the viewer log, the instructions are:
- Log out
- Zip up your viewer logs folder. This page tells you where to find the logs folder for the Second Life viewer. For Firestorm, the instructions are similar but the directory and log file following a 'Firestorm' naming pattern instead of 'SecondLife': https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/
- Email the zip file to bug-attachments@lindenlab.com and reference the issue name in the email subject line.
- Leave a comment on this canny issue (along with details about which viewer you were using) once that's done so we can take a look at the logs.