The program has been experiencing an issue when attempting to connect to a voice channel. When attempting to connect, the program gets stuck mid-way and displays the text "Routing," but never actually connects to the voice channel.

Steps to reproduce the issue:

-Launch the Ripcord program.

-Attempt to connect to a voice channel.

-Observe that the program gets stuck mid-way and displays the text "Routing," without ever connecting to the voice channel.

Additional information: This issue started occurring on March 20th, 2023. No updates to the program or changes to the system configuration have been made since then.

Until now, I have only found a temporary solution that works only on servers where I have power, for obvious reasons. In the rest, I have basically been left without communication because my device does not support the voice chat in the original Discord.

To solve the "Routing" issue in the Ripcord program, please follow these steps:

1 Open the "Discord Original" program. 2 Access the voice channel you wish to use. 3 Edit the voice channel you wish to use. 4 Locate the "Region Override" option. 5 Change the region to one closer to your location. 6 Attempt to join the voice channel again in Ripcord.

By following these steps, you should be able to resolve the "Routing" issue in Ripcord.

The previous method has stopped working, as soon as someone else enters the VC, the connection is lost and it goes back to routing.

@Sen404RCD, I just wanted to drop in and offer you a heartfelt 'Thank you!' for your follow-up about manually overriding a particular voice channel's server region. This is the only thing that we've found that has worked for us to resolve the issue so far.

I know it's not the most ideal situation, but, for us at least, it is a workable solution and has gotten us back up and running for the time being. I really appreciate you taking the time to circle back and update the ticket with that solution once you found it.

In case anyone else sees this and is trying out the manual server override solution themselves, I wanted to post an update myself, to note that, at first, we tried several server regions that were close to us, all to no avail - each time, we returned to Ripcord, opened the voice channel back up, and continued to see the Routing... message, along with no working audio from the other party. The servers we tried and continued to run into issues with were all of the US regions, and then Japan. Figuring it was worth a shot, I decided to continue testing, and, eventually, I tried the Brazil servers and found success!

So, I'm not sure if this is something specific to do with the Discord voice servers in particular regions, or something else entirely, but it doesn't seem to be strictly a proximity or ping issue, as all of the server regions close to us failed, while the Brazil region, which is not particularly close by, ended up working.

Anyhow, I hope that this might help someone else get back up and running with Ripcord voice chat for the time being, and that is also may provide some additional helpful insights to you, @cancel, as well, whenever you are able to turn your attention to resolving this issue.

On that note, many thanks to you as well, @cancel for creating and maintaining Ripcord in the first place!

@Sen404RCD I just saw your latest response after submitting mine. We're currently on an active VC, and it's working great. So either it's an intermittent issue, or maybe a different server region would work for you (as per my previous reply)...

Worth a shot at least.

It also makes me wonder if Discord is rolling out changes around the world in phases, and there just happen to still be some regions that are still working at this point. I have no real information to suggest that though, just brainstorming why things might be changing over time.

Anyhow, maybe try the Brazil region for now, and see if that might work for you for the time being.

Thanks again for the idea/solution!