Party Chat isn't working properly

Thanks maxen for your reply. I did test my friends controller and headset and it worked on his but not on mine.

It was with his and it didn't work on mine but on his. I also bought a new mic and I used my other controller and the result was still the same. My Turtle Beach is also wireless so the chat adapter wasn't used.

Was that with your headset and console, and his controller? If so, it's your controller (or chat adapter) at fault.

It's likely going to be the controller -- or the chat adapter if you have one of those.

One thing to try is to go to Settings > Kinect & Devices > Devices & Accessories and select your controller, then reassign it to yourself and see if you can now be heard in party chat.

Alternatively, do you have another controller (including chat adapter if applicable for older-model controllers) you can test on, or could you borrow one from a friend?

Let us know how you get on.

Hi Toasty,

This may be a temporary issue due to server side (MS Xbox Live) issues.

It is however also worth checking your NAT status. Settings - Network - Network Settings. This will bring up a summary of your network connection. If you have Moderate or Strict NAT this can impact chat. Also get the friends who you are trying to join party
chat with to check as well.

If any of you have 'moderate' or 'strict' NAT this can impact comms. (ideally NAT will be 'open')

If Moderate or Strict NAT is apparent then a router reset may clear the issue. If it does not then there are a whole host of things that can be done to amend home network setup to avoid this - can help with this if needed. I would also urge some caution
before embarking on reconfig of network. I had a similar issue back in March last year and it followed downtime on Xbox Live - spent ages setting up various bits to reduce the likelihood of NAT issues - no joy even though they should of worked - in the end
it was server side and cleared - there were still some problems on the Xbox Live service even though it was back up.

As such it might just be a bit of patience is required and the problem will go away in a day or so. If it does persist then perhaps something server side has changed permanently on how NAT is detected and some home network reconfig may be required.

Cheers,

KiD.