Voice
needs info
Blue Tsuki
Current state of voice is a dumpster fire. Dropped calls, failed calls, sudden local voice failure. The webRTC roll out is a disaster
Log In
Blue Tsuki
OK I hope this is what you need. Voice call was arbitrarily disconnected and multiple attempts by myself and sweetmimixx.resident to re-establish the call failed. Both of us showed that the call was accepted but there was no voice at all. In the reconnect attempts there were also occurrences of looping failure in the IM window which required that the window was closed to stop the looping feedback.This occurred at sim SLB Exhilarate 6-19-2026 between approx 1:05 PM SLT and 1:30 PM SLT. There was NO sim crossing or teleport involved. At this point we gave up and switched to whatsApp for a voice call. I will send the log file "archive.zip" to the bug attachments email you provided as the attach button on this web form only shows the file grayed out when attempting to attach. Since these failures are intermittent and arbitrary I doubt you will be able to reproduce. Blue Tsuki
Maestro Linden
Blue Tsuki: Thanks for the details with region name and time. Once I get the log file (I don't see it yet), I should hopefully be able to compare simulator vs viewer log messages from that time.
Blue Tsuki
Breakwater beach, existing IM call dropped after 2 minutes in the sim. Both users are on 7.2.4.8 of Firestorm. IM call dropped. Attempts to reconnect result in looping failure regardless of who is trying to call. Is that specific enough? Again, this is not the only place this happens.
Maestro Linden
Blue Tsuki: The log file in your latest email (which is
SecondLife.log
) is still from a month ago. Since you're using firestorm, you'll want to look for your Firestorm logs folder. In order to check if a log file is the "correct" one, you can look at the timestamp shown at the beginning of each line. For the SecondLife.log attached to your email, the timestamp starts with 2026-05-11T19:38:58Z
(this is UTC time zone - subtract 7 hours for SLT).Another thing to keep in mind about viewer logs are that they are overwritten each time you launch the viewer. So the next time you launch Firestorm, it will overwrite Firestorm.log from the previous instance of that viewer.
Another thing we want is a basic timeline of the event, so we know where to look in the logs. Something like this:
> 1. 08:40:30 SLT : Blue.Tsuki (in Ahern) calls Ruth (in Suduffco)
> 2. 08:40:40 : Ruth clicks to accept the call, call connects successfully
> 3. 08:42:00 : Ruth teleports from Suduffco to ANWR
> 4. 08:42:05 : Blue.Tsuki's viewer reports that the call dropped
> 5. 08:43:00 : Ruth's viewer reports that the call dropped
> 6. 08:44:30 : Blue.Tsuki attempts to call Ruth again, but Ruth's viewer does not show the incoming call notification. Instead, Ruth's keyboard catches on fire.
For what it's worth, I moved two Firestorm 7.2.4 (80712) users to https://maps.secondlife.com/secondlife/Breakwater%20Beach/166/113/22 , then started a p2p call between them. It was holding strong for about 30 minutes, at which point I gave up reproducing the call drop.
We have a known issue about p2p calls sometimes being dropped after a region crossing or teleport, but from your description it sounds like you weren't doing either of those during the call.
Maestro Linden
Merged in a post:
Voice continues to fail across the grid
Blue Tsuki
IM voice calls drop without crossing sim boundaries. IM voice calls fail to connect on both ends. Web RTC has been a massive fail and you know it!
Blue Tsuki
In the past I never had issues with dropped calls or failure to connect. This is all new since WebRTC. This happens regardless of location, sim or the person you are talking with or calling. It happens with both parties. We have tried toggling voice, turning off voice when teleporting and using the gear button in profiles to make calls. The failures are arbitrary and irregular. Sometimes things work but once there is a failure all further attempts to reconnect/connect, fail.
Maestro Linden
Hi Blue Tsuki , as mentioned in your original report (which seems to report the same issue), we need details of specific incidents in order to investigate.
Blue Tsuki
I have been asked to give more logs. I am starting to feel like a QA tester. I am now using the newest Firestorm beta and continue to have voice failures as previously described. The most egregious is the failure of IM calls to connect in either calling or being called. Also IM calls that do manage to connect are disconnected when moving to another sim either by TP or just walking. Again it does not matter where you are or what you are doing. The problem is systemic. I see from this thread I am not alone in these failures and frustration.
Ripley Radek
I've had the same problem. If my friend and I are going to go to other sims while in chat we use the Discord for chat since Second Life's does not work. The so called "fix" of voice did nothing to improve things.
Sijora Ravenwood
But there is apparently speculation that most fake users in SL don't use voice anyway and the rest will give up complaining at some point, completely annoyed, especially since you can't even submit a bug report. Time to finally cancel my premium account!
Sijora Ravenwood
I do have the same problems! That is not a single problem of some users, and YOU LindenLab know that!
Blue Tsuki
This is a systemic problem not limited to specific sims. Both users are running Firestorm Beta 7.2.4.80703. IM calls are dropped after teleport. Attempts to reconnect by both users yield the same results: the caller only sees the "connecting" message while the receiver sees the invitation and accepts with no connection established. Sometimes the call attempt yields a looping message failure where the chat window says "connecting" then fails and loops until the window is closed. If you are sailing in the Blake sea and you are in a call, it will drop after sim crossing. We have been advised to turn off voice before teleporting and also to try calling via the gear in Avatar profile. Occasionally this will work but mostly not. I have also experienced a local voice chat arbitrarily stop working. I have used IM voice since it was introduced. I have never had this much trouble. I am on a Mac OS 13.6.9, iMac 27" i9 with upgraded AMD Radeon Pro Vega48 graphics. Graphics are not a problem. I have created a 300KB logs.zip file as instructed however when trying to attach it to this report it fails telling me it is "invalid" exceeding 8MB.(???) If I move the zip file out of the library it is visible in the finder but when attempting to attach to this message it is grayed out in the dialog file picker. I will email it instead to the address given below along with a copy of this text.
Maestro Linden
updated the status to
needs info
Hi Blue Tsuki, I have a few questions for you:
- Which environment are you seeing issues under? Please include your 'About Second Life' or 'About Firestorm' text for each of the users involved. Please note that Firestorm 7.2.3 release has a number of known bugs with voice compared to either Second Life Release 26.2.0.25386466510 or the Firestorm beta 7.2.4 (80703). The full text includes valuable information about your system.
- Is this issue generally reproducible? If so, include step-by-step instructions for how to reproduce it, along with expected vs actual behavior so that we can investigate it in-house.
- If the issue is notgenerally reproducible, we'll need details about specific incidents. Since you're talking about calls, we need info about both agents involved in the call, as the viewer or server either end could be at fault. The details we need are:
- Details of which agents were involved in the failure, which viewers they were using, and which regions they were in at the time.
- Steps to leading up to the issue, including timestamps for each step along of the way. Something like this:
> 1. 08:40:30 SLT : Blue.Tsuki (in Ahern) calls Ruth (in Suduffco)
> 2. 08:40:40 : Ruth clicks to accept the call, call connects successfully
> 3. 08:42:00 : Ruth teleports from Suduffco to ANWR
> 4. 08:42:05 : Blue.Tsuki's viewer reports that the call dropped
> 5. 08:43:00 : Ruth's viewer reports that the call dropped
> 6. 08:44:30 : Blue.Tsuki attempts to call Ruth again, but Ruth's viewer does not show the incoming call notification. Instead, Ruth's keyboard catches on fire.
- Viewer logs from the 2 parties involved. To send viewer logs,
- Log out
- Zip up your viewer logs folder. This page tells you where to find the logs folder: 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 once that's done so we can take a look at the logs.
Maestro Linden
Ripleigh Resident Sijora Ravenwood If you're hitting specific voice issues, please file a new ticket in this feedback portal and provide the details I've requested to Blue above.
Sijora Ravenwood
Maestro Linden, thank you but all this is "eyewashing". actually I am cleaning my Premium parcel, then I'll cancel the premium account. Maybe from time to time I will have a look inside Secondlife again....but to be honest: that is VERY maybe. Meanwhile I am sick and tired of constanly being strung along and jerked around (and actually paying money for the privilege). With all due respect to your work, it is Linden Lab's new "marketing" that is driving usersaway. at least some of them. Those who never were REALLY interested in SL itself, of course will stay. Goodbye and all the best for your future!
Maestro Linden
Blue Tsuki Thanks for sending the viewer logs. However, it looks like that particular viewer session was from May 11, which was before the server-side fix for https://secondlife.canny.io/server-bugs/p/voice-disconnects-when-you-teleport
came out to any regions. The fix for this bug went out grid-wide on May 19.
If you have any more recent incidents, could you attach those viewer logs? Note that Firestorm viewer sessions fall within an 'Firestorm' folder rather than the 'SecondLife' folder, so you'll have to modify the instructions when reproducing on that viewer.
Also, as I mentioned in point (2) of the parent comment, it would be very helpful to include some annotation about what you were doing in-world (with timestamps) so that we can get context for the events found in the viewer log.
There is a known issue that if you region cross aggressively enough (several times a minute), there's a ~20% chance that a given crossing can terminate the call. It would be helpful to know if your call was dropped after just a single crossing or if it occurred after several crossings.
Load More
→