Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Other Vivox Undocumented Error

Discussion in 'Vivox (Voice & Text Chat)' started by amw030, Apr 25, 2022.

Thread Status:
Not open for further replies.
  1. amw030

    amw030

    Joined:
    Jan 2, 2020
    Posts:
    1
    Before the weekend, the login was working fine for Vivox. Now, I receive these errors:

    <BeginGetConnectorHandle>b__0: vx_req_connector_create_t failed: VivoxUnity.VivoxApiException: (11175)
    at VivoxUnity.VxClient.EndIssueRequest (System.IAsyncResult result)
    <BeginLogin>b__0: BeginGetConnectorHandle failed: VivoxUnity.VivoxApiException: (11175)
    at VivoxUnity.AsyncResult`1[T].get_Result () [0x0000e]
    Error: (11175)

    It is still functioning in that I can hear my partner when in multiplayer mode and he can hear me, but I'd like to resolve the new errors. I've seen the same issue posted on the old Vivox Forum, but its "resolution" was that it was an internal error and Vivox remedied it.
     
  2. emilyryan

    emilyryan

    Unity Technologies

    Joined:
    Nov 22, 2019
    Posts:
    129
    Hello!

    I am sorry to hear you are experiencing these errors. A few follow up questions to help analyze the issue:
    • Are you seeing these errors 100% of the time when logging into Vivox?
    • Have you added any anti-cheat software to your game?
    • Which domain do you use for Vivox services? For example, check your credentials either through the developer portal or the Unity Dashboard and respond with the value under domain. For example: mt1s.vivox.com
      • Unity Dashboard steps: Go to the Unity Dashboard, select your project from the dropdown, select Multiplayer Services, select Vivox, select credentials
      • Vivox Developer Portal steps: Go to developer portal, select app dashboard, select your app
    NOTE: PLEASE DO NOT SEND A SCREENSHOT OF YOUR CREDENTIALS. PLEASE KEEP YOUR ISSUER AND KEY PRIVATE
     
  3. megbal

    megbal

    Joined:
    Sep 18, 2022
    Posts:
    4
    Since roughly the time when this thread was created the Overwatch voice chat which also uses Vivox is broken for me and many others. The game just says "Voice chat error 11175" once and never joins any voice chat. Asking Blizzard support is futile and just results in generic copy/paste troubleshooting that doesn't seem to help anyone.

    I was looking for any info/solutions and found this thread which looks potentially related. The Overwatch log (relevant portion included below) also indicates a connection problem. I've tried using some VPNs to rule out router/ISP issues but that doesn't help.

    Is there any info to be had what exactly this error 11175 means so I can maybe troubleshoot the issue? Or something that can be done to reverse whatever broke it in the first place? Overwatch voice chat was working fine for all the years prior to this.

    From the log:

    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.341Z]: ==[VC] JoinVoiceChannel() _?__U0w==__?_ - MATCH - active = 1
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.341Z]: ==[VC] Request channel transmit 259761146 (true)
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.341Z]: ==[VC] Request join channel MATCH 259761146 8f7ba3fa
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.341Z]: ==[VC] Request login xxxxxxxx
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.341Z]: ==[VC] Login credentials requested
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.841Z]: #=[VC] LoginCredentials b 0 xxxxxxxx xxxxxxxx xxxxxxxx
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.841Z]: ==[VC] Connect requested 05020230 7d33d227
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.974Z]: #=[VC] ResponseConnect 0b 2(11175:811c9dc5) 811c9dc5
    [18816] [ERR] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.991Z]: ==[VC] Connect failed 11175 7d33d227
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.991Z]: ==[VC] Request stop
    [18816] [NRM] [VoiceChat] [External(0)] [External()] [2022-09-18T12:38:04.991Z]: ==[VC] Cancel all queued trackers 3
     
    satoshi_jp likes this.
  4. UnityKip

    UnityKip

    Unity Technologies

    Joined:
    Nov 15, 2021
    Posts:
    36
    Hi @megbal

    Is this issue still ongoing? Are you consistently unable to login to voice or does it work sometimes?

    Unfortunately, we're not able to troubleshoot user issues for live games on this forum. Blizzard (and developers in general) are able to contact us directly if they have an impacting event that originates from Vivox.

    With that said, if you let us know what you're seeing we may be able to correlate your experience and logs to internal logging on either side that might help us track down an issue. Lastly, this particular error is not known to manifest client-side. Unless you have made any notable changes to your environment or updated/added a new antivirus software, I suspect the issue to be on the backend somewhere and no further action should be required from you.

    -Kip
     
  5. megbal

    megbal

    Joined:
    Sep 18, 2022
    Posts:
    4
    This is ongoing and hasn't been working at all for many months. Initially when it started the game would give you a big error 11175 message as soon as the main menu appeared. At that point there is no voice chat to join so the game is just pinging or authenticating to the vivox server.

    Blizzard must be aware of the issue because 1-2 months ago the message was semi-hidden and is only seen under certain circumstances. For me I must have auto-joining of voice chat turned on in the game options, otherwise I'll never see the message. If I do have it on, when I join for example the training room (which will have voice chat) I usually see the message but not always, which kinda feels like someone "solved" it by making the error mostly disappear so their support can keep sending everyone to fairytale troubleshooting land.

    The game will only ever show the error once and note "#=[VC] Error displayed to user 11175" in the log file. Speaking of which, probably few people know there's a log at all and that it holds the real info you might want to know, like how every new match the game tries to connect to the VC and fails with error 11175. And that it does successfully initialize the correct input/output devices prior to that. If VC would work you'd get a "X players in voice chat" text in the game-chat, but that never happens anymore.

    Indeed nothing changed about my client PC so it was almost certainly a bump in the vivox client/server version, but there must be something I can do to make my client work with it again now instead of crossing my fingers and hoping for the next version. Incidentally I even tried replacing the game's vivoxsdk.dll with different versions but you can probably guess how that went (no I don't want to send a crash report).

    This is how an in-game error looks like but in this case instead of "[3]" it says "[11175]". The description text is the same but misleading and just a default. As I explained you never join a voice chat so you couldn't be "removed".

     
  6. megbal

    megbal

    Joined:
    Sep 18, 2022
    Posts:
    4
    Some days ago Overwatch had a notice in the launcher that they would do voice chat maintenance for a few hours during which vc will be unavailable.

    This error still persists however as of right now.
     
  7. megbal

    megbal

    Joined:
    Sep 18, 2022
    Posts:
    4
    The issue persists after Overwatch downgraded to the Overwatch 2 client.
    @UnityKip
     
  8. emilyryan

    emilyryan

    Unity Technologies

    Joined:
    Nov 22, 2019
    Posts:
    129
    Hello! Thank you for the additional information.

    Unfortunately, with the information above, we can only suggest that you try and each out to the game developer again. Thank you for your time and cooperation and we wish you the best!
     
Thread Status:
Not open for further replies.