[BUG-20075] "We're having trouble connecting to your voice server" at login occurs much more frequently lately

[sl-service-account]

Steps to Reproduce

• Login to any region that has voice enabled.

• Observe whether voice connects.

  Observed Behaviour

• Over the 3 weeks or so, fairly often when logging into any region, voice will fail to connect & you will get this error message in the viewer:

  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.

• Voice will never connect no matter how long you wait & the speak toolbar button remains greyed out.

• While still on the same region, if you go to Preferences -> Sound & Media & disable then enable voice chat, voice will then connect on that same region & voice chat will behave as expected for the rest of the session.

• Even when logging into regions or parcels that have voice chat disabled, you will still get the "We're having trouble connecting to your voice server" error in the viewer.

• I'm fairly sure this recent problem isn't a problem at my end because others have been complaining about this happening much more frequently lately.
  I have exactly the same problem on Firestorm viewer too.
  Note that I'm using a Firestorm version that has coroutines merged in - I'm unsure yet if this problem is only affecting coroutine viewers.

• Logs attached from a session where I reproduced this on default release (as in system information) - Whirly_1.log.

• When voice fails to connect at login, logs show:

  2016-06-22T13:40:35Z WARNING:#Voice LLVivoxVoiceClient::loginToVivox: too many login retries or timeout connecting, giving up.
  2016-06-22T13:40:35Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: 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.

• After I disable & enable voice & voice connects as expected, logs show:

  2016-06-22T13:42:46Z INFO:#Voice LLVivoxVoiceClient::connectorCreateResponse: Connector.Create succeeded, Vivox SDK version is 4.6.0017.22050 connector handle Q32bZci4YT8U
  2016-06-22T13:42:46Z INFO:#Voice LLVivoxVoiceClient::waitForChannel: Waiting for channel
  2016-06-22T13:42:50Z INFO:#Voice LLVivoxVoiceClient::sendLocalAudioUpdates: Setting speaker mute to false
  2016-06-22T13:42:50Z INFO:#Voice LLVivoxVoiceClient::sendLocalAudioUpdates: Setting speaker volume to 62
  2016-06-22T13:42:50Z INFO:#Voice LLVivoxVoiceClient::sendLocalAudioUpdates: Setting mic volume to 50
  2016-06-22T13:42:58Z INFO:#Voice LLVivoxVoiceClient::requestParcelVoiceInfo: Voice URI is sip:confctl-166316827@bhr.vivox.com
  2016-06-22T13:42:58Z INFO:#Voice LLVivoxVoiceClient::runSession: running new voice session 
  2016-06-22T13:42:58Z INFO:#Voice LLVivoxVoiceClient::addAndJoinSession: Adding or joining voice session 
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::sessionCreateResponse: Session.Create response received (success), session handle is 3
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::addAndJoinSession: event=<llsd>
      <map>
      <key>handle</key>
          <string>3</string>
      <key>session</key>
          <string>created</string>
      </map>
  </llsd>
  
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::sessionAddedEvent: session sip:confctl-166316827@bhr.vivox.com, alias , name  handle 3
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::addAndJoinSession: event=<llsd>
      <map>
      <key>handle</key>
          <string>3</string>
      <key>session</key>
          <string>joined</string>
      </map>
  </llsd>
  
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::sendLocalAudioUpdates: Setting speaker volume to 62
  2016-06-22T13:42:59Z INFO:#Voice LLSpeakerVolumeStorage::load: Loading stored speaker volumes from: C:\Users\Whirly\AppData\Roaming\SecondLife\whirly_fizzle\volume_settings.xml
  2016-06-22T13:42:59Z INFO:#Voice LLVivoxVoiceClient::joinedAudioSession: added self as participant "W͠h͡i�rl͞y͠ �F͞i͠z͡zl�e͠" (2e255955-e183-48c4-b9f9-1cd1b80db94e)

  Expected Behaviour

  Less failures of voice to connect at login.

Attachments

• VivoxVoiceService-2016.09.09.zip 2016-09-10 00:18:32
• Whirly_1.log 2016-06-22 10:02:38
• Whirly_2.log 2016-06-26 01:18:15
• Whirly_3_extra_logging.log 2016-09-10 00:18:32

Links

Related

• [BUG-10230] [Project Azumarill] Voice often fails to connect on the Azumarill viewer #584
• [BUG-37640] voice server issue #11978
• [BUG-40466] [Aditi] Voice fails to connect on several Aditi regions (for Kyle) #12141

Original Jira Fields

Field	Value
Issue	BUG-20075
Summary	"We're having trouble connecting to your voice server" at login occurs much more frequently lately
Type	Bug
Priority	Unset
Status	Accepted
Resolution	Accepted
Reporter	Whirly Fizzle (whirly.fizzle)
Created at	2016-06-22T13:45:30Z
Updated at	2016-09-10T04:18:32Z

{
  'Business Unit': ['Platform'],
  'ReOpened Count': 0.0,
  'Regression?': ['Issue is a Regression'],
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Filling in...',
  'What were you doing when it happened?': '...',
  'What were you expecting to happen instead?': '...',
  'Where': 'Any region',
}

[sl-service-account]

Whirly Fizzle commented at 2016-06-26T05:17:58Z

• Just reproduced this problem again while on Second Life 4.0.5.315117 (Second Life Release)
• Logged in at http://maps.secondlife.com/secondlife/Zarahemla/219/231/25
• Got the "We are having trouble connecting to your voice server" error.
• Waited a few mins & voice stil did not connect.
• Disabled then enabled voice & it connected.
• Log attached - Whirly_2.log.

[sl-service-account]

Whirly Fizzle commented at 2016-09-10T04:16:38Z

Just reproduced this on Second Life 4.0.7.318301 (Second Life Release) with VivoxDebugLevel set to -3.
Attached:

• Whirly_3_extra_logging.log
• VivoxVoiceService-2016.09.09.log