Well, last night, we logged in, this time we didn't enable use Vivox voice first but, instead, we went straight over to WebRTC1. If I didn't mention this before, we're both on Firestorm. When I attempted to talk, I couldn't broadcast for some reason (I had no green lines but I saw hers) although I could hear her in Open Voice. But, her voice wasn't coming into my headset, even though it was configured to do so. It seemed like the viewer was forcing the voice to go directly to my external speakers. Changing the configurations in SL or Windows had no effect. That was very baffling. So, I then tp'd home to Vivox land and immediately my open voice worked. So, I went back to WebRTC1, open voice still didn't work (but private voice did) so I logged out and back in at WebRTC1 and everything (open & private) seemed to be working fine, voice went into my headset, green lines, audio quality, etc. All good for me.

For my partner, in Open Voice, after i relogged, she continued to see my lines as red lines (I saw mine as green) even though my voice was not clipping and sounded normal to her. But she was not able to use her Nearby voice slider to make any changes to my voice either. If she turned it down to zero, my voice was still at a normal listening level to her. Same thing if she cranked it to max. She then muted/blocked me and saw me go gray. But, my voice continued and she could still hear me. When I tried that with her, she turned gray and her voice was muted. So, she relogged at WebRTC1. Same thing. Relogged again. Same thing.

Audio-wise, we both heard each other fine (after we had relogged). It was just a bunch of quirky things outside of the audio quality. But... and this is concerning... we stayed there in open voice for almost 35 minutes but we had to leave because the voice just suddenly stopped working for both of us. And we couldn't get it back. We couldn't even call each other in private. When we tp'd back to Vivox land, everything returned to normal.

I will try the Linden viewer this weekend and report back.

Dion Robbiani: Thank you and I look forward to the test results from the Beta viewer. It has several fixes that are not yet in the FireStorm viewer. Eg. plugging/unplugging headphones works much better.

Well, Dan, we tried to test on Sunday and it went downhill pretty quick. We were in Vivox voice when we both tp'd into WebRTC1 and, of course, our connection was dropped. We both saw our green lines but we couldn't hear the other. So, after about a minute, we tp'd back out to our home and then discovered we couldn't do open voice anymore there (yellow chat). We also couldn't see our white dots. So, initially, we didn't think we could even do a private call, but, we tried anyway and were able to connect up. But... neither of us could hang up. So, we both logged out, rebooted our computers, came back, problem was still there in our home sim. I tp'd back to WebRTC1 and I did see the green chat again. However, my partner refused to return. We eventually went to a sandbox, open voice appeared to work there and we saw green again, finally. We were too afraid to go back and test... we believe somehow WebRTC messed up our Vivox voice. As of when I finally logged out, I still couldn't end a Vivox call (no red icon, although she could). So, even though we couldn't test the quality of the voice, maybe this report will let you know what other problems people might run into outside of the call connection itself.