sl-service-account
commented
5 years ago Whirly Fizzle commented at 2019-01-02T01:14:23Z
Hello KnightsPet ,
There is a voice outage on all the grid at the moment affecting the majority of people. This time it's caused by a vivox DNS outage & should be fixed in less then 24hrs. Firestorm support got hold of a Linden this morning who explained its due to the TTL and polluted DNS cache on the systems in between which neither LL nor vivox control.
I'm not sure why there is no grid status update yet.
What just happened?
We're having trouble connecting to your voice server:
https://www.bhr.vivox.com/api2/ :UDP: 3478, 3479, 5060, 5062, 12000-17000
Voice communications will not be available. Please check your network and firewall setup.
What were you doing when it happened?
i froze up and went to reboot when i came back sl voice went down for me and posted this message We're having trouble connecting to your voice server:
https://www.bhr.vivox.com/api2/ :UDP: 3478, 3479, 5060, 5062, 12000-17000
Voice communications will not be available. Please check your network and firewall setup.
been trying for two days for it to work
What were you expecting to happen instead?
i have reinstalled firestorm many times contacted my internet provider nothing i have updated my drivers nothing
Other information
how do i fix it
Links
Duplicates
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-226043 | | Summary | SL VOICE DONT WORK FOR LAST TWO DAYS FOR ME | | Type | Bug | | Priority | Unset | | Status | Closed | | Resolution | Duplicate | | Reporter | KnightsPet (knightspet) | | Created at | 2019-01-02T01:00:14Z | | Updated at | 2019-01-02T15:44:20Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2019-01-01T19:14:22.818-0600', "Is there anything you'd like to add?": 'how do i fix it', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': "We're having trouble connecting to your voice server:\r\n \r\nhttps://www.bhr.vivox.com/api2/\r\n:UDP: 3478, 3479, 5060, 5062, 12000-17000\r\n \r\nVoice communications will not be available.\r\nPlease check your network and firewall setup.", 'What were you doing when it happened?': "i froze up and went to reboot when i came back sl voice went down for me and posted this message\r\nWe're having trouble connecting to your voice server:\r\n \r\nhttps://www.bhr.vivox.com/api2/\r\n:UDP: 3478, 3479, 5060, 5062, 12000-17000\r\n \r\nVoice communications will not be available.\r\nPlease check your network and firewall setup.\r\n\r\nbeen trying for two days for it to work", 'What were you expecting to happen instead?': 'i have reinstalled firestorm many times contacted my internet provider nothing\r\ni have updated my drivers nothing', 'Where': 'windows 10\r\nchromeFirestorm 5.1.7 (55786) Jul 13 2018 20:00:04 (64bit) (Firestorm-Releasex64) with Havok support\r\nRelease Notes\r\n\r\nCPU: AMD E2-9000e RADEON R2, 4 COMPUTE CORES 2C+2G (1497.19 MHz)\r\nMemory: 3982 MB\r\nOS Version: Microsoft Windows 10 64-bit (Build 17134)\r\nGraphics Card Vendor: ATI Technologies Inc.\r\nGraphics Card: AMD Radeon(TM) R2 Graphics\r\n\r\nWindows Graphics Driver Version: 23.20.768.12\r\nOpenGL Version: 4.2.13497 Compatibility Profile Context 23.20.768.12\r\n\r\nRestrainedLove API: (disabled)\r\nlibcurl Version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.8 nghttp2/1.25.0\r\nJ2C Decoder Version: KDU v7.10.4\r\nAudio Driver Version: FMOD Studio 1.10.05\r\nDullahan: 1.1.1080 / CEF: 3.3325.1750.gaabe4c4 / Chromium: 65.0.3325.146\r\nLibVLC Version: 2.2.8\r\nVoice Server Version: Not Connected\r\nSettings mode: Firestorm\r\nViewer Skin: Firestorm (Grey)\r\nWindow size: 1366x705 px\r\nFont Used: Deja Vu (96 dpi)\r\nFont Size Adjustment: 0 pt\r\nUI Scaling: 1\r\nDraw distance: 128 m\r\nBandwidth: 500 kbit/s\r\nLOD factor: 2\r\nRender quality: Medium-High (4/7)\r\nAdvanced Lighting Model: No\r\nTexture memory: 1024 MB (1)\r\nVFS (cache) creation time (UTC): 2019-1-2T0:17:20 \r\nBuilt with MSVC version 1800\r\nJanuary 01 2019 16:59:21 SLT\r\n', } ```