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
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
marked this post as
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.