Voice calls not connecting.

[Oakshadow]

This isn't specific to the most recent patch. However now that voice chatting in group chats is easier it's more obvious that it isn't working.

Whenever I try connecting to a group voice chat room it says I'm connecting until it eventually drops out altogether. This has been happenign for awhile but I don't know what changed on my PC to cause it to do so.
I use a webcam mic for voice chat and monitor speakers. I know both work as when I test them in the steam settings both work.

It shouldn't be software firewall issue. However I don't have any manual ports forwarded for my router as it's default settings already open ports for steam. It is an old router though so I'm wondering if the voice ports for Steam have changed? Or if there are any known windows 10 settings (such as within internet explorer) that would hinder my ability to connect. (as I tend to lock down internet explorer given that I don't use it.)

Edit: forwarded all relavent ports via Windows firewall and the router... nothing works.

Any help would be appreciative. Thanks!

[berkanx]

Same here.
------------------------------------------------------------------------------------------------------------------------------
Almost all my friends not using antivirus and theirs are working. So I turned off kaspersky, windows defender, firewall, modem's firewall etc. everthing. I opened all port about Steam. I updated all drivers, windows update. But it's not worked.
------------------------------------------------------------------------------------------------------------------------------

Originally posted by LosTZiLLA ✜:

Same problem here. But there's something interesting. If I connect via the internet from my cell phone, voice chat works perfectly without changing anything else. It seems like it's some problem with my internet provider, however, the old voice chat worked normally.

I tried and it's worked so maybe that's not about firewall or something. This's just a temporary solution.
------------------------------------------------------------------------------------------------------------------------------
New Steam Update (08-01-2018)
And still not working.
------------------------------------------------------------------------------------------------------------------------------
Steam published this article. (08-04-2018)
https://support.steampowered.com/kb_article.php?ref=2598-RTZB-6114
Check this out. It may fix your problem.

[Kei]

Same here.

[Wa$tedpotentiaL]

i tried everything firewall off still not working

[Coxis]

It's happenning to me too... none of my friends have this issue.

[iaguin_du_caum]

It's happenning to me too... none of my friends have this issue
+
allowing UDP connections through port 27015 in the firewall made no difference, deactivating anti-virus made no difference
+
in my case, it's surely not anything with the router, because it worms with a laptop connected to the same network the pc is.
+
steam clearly reconizes the mic in the settings > voice menu. it's just clearly not connecting. the audio logs show the connection doesn't complete

it seems that was a known issue while in beta and it was released as such '-'

[Oakshadow]

Thanks, I didn't see it when I searched for the issue. Hopefully they patch it soon. I sent a ticket into support. If I recieve any special instructions that work I'll be sure to post it here.

[Wanderley das idéia errada]

Same problem here.
Try to email a Valve dev and I get this answer: "It’s a problem with your network either blocking the outbound traffic or not forwarding UDP packets returned to the same source port that you sent from. Unfortunately since network/router/firewall setups vary so widely I can’t tell you exactly what setting to fix or change on your network."

Already try:
- Disable WIndows Defender (I don't have any firewall)
- Port forward port 27015 UDP (and also check if is working: https://i.imgur.com/GkVELH6.png).
- Clean reinstall Steam.
- Change to beta cliente and back again to normal cliente.
- Make a selective startup on Windows to disable all third-party programs running in the background.
- Star Steam on TCP mode.
- Restart the PC, modem and Steam.
- Disable QoS on my modem.
- Set my IP as DMZ on my modem.

[Suku]

Neither here, they changed the way to connect to use UDP ports I guess, but I can't forward them neither

[Wanderley das idéia errada]

Originally posted by The Professor:

Neither here, they changed the way to connect to use UDP ports I guess, but I can't forward them neither

This is not a port problem. I try to run Steam on Win7 Compatibility and work for me at the first time but don't work anymore after I try to connect in another server.
So this maybe help, but didn't work 100% of time. Some times you need try to connect multiple times after you really connect.

So this is a Steam bug related for how use Win 10. In my case I using the last version 1803 (Build 17134.165).

[iaguin_du_caum]

well, I use win7 and got the problem...
Got this response when I sent audio logs to a valve dev:

"Your log shows that your client chose the open port 55817 on your end, and then is sending to us on 27015 as expected.

However, you aren’t able to both send and receive UDP traffic. So either a software firewall is blocking it for outbound 27015, or it’s blocking responses back from us with a src port on our side of 27015 but a dest port on your side of 55817. Or you have some router setup that is not forwarding the UDP traffic and doing NAT correctly for UDP. Note that the port on your side won’t always be 55817, your client will choose an available port and you need UDP port forwarding and NAT to work generally. You’ll have to figure out a resolution to this, unfortunately I can’t provide much more detailed help since network setups vary so much.

Since this works ok for you on another device on your network, I would guess in your case that this is a local machine / firewall / security software issue blocking the traffic, rather than a router issue."

Well, I deactivated every possible security software...firewall, anti-virus, anti-spy, etc...and nothing changes.

The issue could be my gamepad drivers, as far as I'm concerned '-'

[Wanderley das idéia errada]

Originally posted by iaguin_du_caum:

well, I use win7 and got the problem...
Got this response when I sent audio logs to a valve dev:

"Your log shows that your client chose the open port 55817 on your end, and then is sending to us on 27015 as expected.

However, you aren’t able to both send and receive UDP traffic. So either a software firewall is blocking it for outbound 27015, or it’s blocking responses back from us with a src port on our side of 27015 but a dest port on your side of 55817. Or you have some router setup that is not forwarding the UDP traffic and doing NAT correctly for UDP. Note that the port on your side won’t always be 55817, your client will choose an available port and you need UDP port forwarding and NAT to work generally. You’ll have to figure out a resolution to this, unfortunately I can’t provide much more detailed help since network setups vary so much.

Since this works ok for you on another device on your network, I would guess in your case that this is a local machine / firewall / security software issue blocking the traffic, rather than a router issue."

Well, I deactivated every possible security software...firewall, anti-virus, anti-spy, etc...and nothing changes.

The issue could be my gamepad drivers, as far as I'm concerned '-'

Yeah, I email John McCaskey from Valve too and get the same ctrl+c answer.

[Oakshadow]

So I've continued to tinker its definitely not a network issue. At least not for myself. My only guess is that either I have a required windows service turned off, another program is interfereing, or it's a bug on Valve's end that effects certain hardware. A strong possiblitiy as both my motherboard and processor are almost a decade old. Unfortuantely the response I got from Valve wasn't very helpful. Frustrating misunderstandings aside, the bottom line was that they currently had no fix for the problem I was experiencing. I just hope the issue ends up on their todo list.

[iaguin_du_caum]

Originally posted by Jay:

So I've continued to tinker its definitely not a network issue. At least not for myself. My only guess is that either I have a required windows service turned off, another program is interfereing, or it's a bug on Valve's end that effects certain hardware. A strong possiblitiy as both my motherboard and processor are almost a decade old. Unfortuantely the response I got from Valve wasn't very helpful. Frustrating misunderstandings aside, the bottom line was that they currently had no fix for the problem I was experiencing. I just hope the issue ends up on their todo list.

that, yeah :(

[Wanderley das idéia errada]

Originally posted by Jay:

A strong possiblitiy as both my motherboard and processor are almost a decade old.

I have a Intel 8 gen processor. Hardware can't be the problem. Drivers versions... Maybe.

[treygolinik]

I have the same :(
Even the reinstallation of Steam did not help