This page contains tips on audio troubleshooting.
These audio setup tips have been collected through the various community forum discussions. They assume that other aspects are working correctly. I.e., that you can connect your client to the server, logon, and move around the world.
Please improve this page with any tips you have.
Where do I start to look for problems?#
Here are some prerequisites you will need to start debugging the problem.
First check that your client is using the correct audio device on your local machine. Then try using the audio recorder in-world to record and playback some audio. These 2 tips are detailed in the overall troubleshooting guide.
Understand the basics of communication between the client and server components. Here are the ports that need to be open or mapped in the firewall You may also need to open port 5060 for TCP
The deployment architecture of Wonderland and how the components communicate via those ports are described in the related troubleshooting guide.
Audio Client Test:
Port testing: You may need to check if your darkstar or voicebridge is listening on particular ports when they are running. This is easy for TCP communication but harder for UDP. For TCP you can run the following on a Unix based server (or if you have cygwin or similar on windows):
> netstat -an | grep 6668 tcp6 0 0 [::]:6668 [::]:* LISTEN
Server Configuration and Logs: You will need to set properties for the server components and examine or send log files.
Client and Server on same machine#
Client and Server on different machines but on same network#
Client and Server on different machines separated by a firewall#
Issue: Voicebridge starts but cannot connect with the Darkstar server
By default, the Darkstar server should be listening on port 6668 for connections from the voice bridge.
With a NAT firewall, your server will have both an internal and external IP address.
Let us assume the following addresses:
- 172.xxx: internal address
- 85.xxx: public address
- the wonderland webserver is exposed on port 8080
- voicebridge.webserver.url http://172.xxx:8080/
- voicebridge.status.listeners 172.xxx:6668
- voicebridge.local.hostAddress 172.xxx
- wonderland.web.server.url http://172.xxx:8080/
- voicebridge.server.public.address 85.xxx
The Darkstar server properties should be:
- wonderland.web.server.url http://172.xxx:8080
The my.run.properties file should include:
With this setup (which may be different than the one listed on the wiki), you should have all internal communication between services on the internal 172.xxx address, but all clients connecting through the public 85.xxx address.
Issue: Darkstar server and Voicebridge server are connected but their is no sound in the clients
If the Voicebridge is connected to the Darkstar server you should see the following msg in the Voicebridge log
[java] Dec 3 19:24:39.777 Successfully notified /172.xx.xx.xx:6668 that this bridge is up
In the client java console you will see a msg like:
org.jdesktop.wonderland.client.softphone.SoftphoneControlImpl lineReceived WARNING: WARNING: No Response to STUN request: Receive timed out
Generate an client audio log report as follows by selecting the following from the client menu
Tools -> Audio -> Log Audio Problem
TBD when I solve the problem...