What steps will reproduce the problem?
1. Launch and log into the Wonderland client.
2. On login, one will observe a pop-up window with the error message "Softphone
Exited, attempting to restart".
3.
What is the expected output? What do you see instead?
The expected output is for audio to work normally without error.
Clicking on the "Reconnect" button in the above window has no effect, and logs
this in the client error log:
WARNING 8:29:03 PM
org.jdesktop.wonderland.client.softphone.SoftphoneControlImpl startSoftphone
Launching communicator: /opt/jre1.7.0_10/bin/java -Dsun.java2d.noddraw=true
-jar /home/dave/.wonderland/0.5-dev/softphone/softphone.jar -mc -u Dave -r
wonderland-zone.davek.co.nz;sip-stun:5060 -stun
wonderland-zone.davek.co.nz:5060 -t 10 -l 192.168.1.1
The softphone however never successfully connects.
Clicking on the "Reconfigure..." button in the above window does not display an
audio configuration window and otherwise has no effect.
Clicking on "Tools -> Audio -> Test Audio" in the Wonderland client does not
display an audio test window, and logs this in the error log:
WARNING 8:29:30 PM
org.jdesktop.wonderland.modules.audiomanager.client.AudioManagerClient testAudio
Unable to run line test: Stream closed
The behaviour is 100 percent consistent.
What version of the product are you using? On what operating system?
Open Wonderland nightly build running on a private server with OpenIndiana
oi_151a7 and Java JDK 6 update 37. Ubuntu 12.04 x86 is the client, running Java
7 update 10.
Please provide any additional information below.
The workaround described at the following thread of running the softphone
separately works:
https://groups.google.com/forum/?fromgroups=#!topic/openwonderland/XVNWhE4FIQg
Additionally, once the softphone is run in tandem with the Wonderland client
the first time, subsequent launches of the Wonderland client without the
softphone also running in tandem do not appear to exhibit any audio error or
issues. Clearly however users should not be expected to do this.
Original issue reported on code.google.com by davekoelmeyer@gmail.com on 19 Jan 2013 at 8:24
Original issue reported on code.google.com by
davekoelmeyer@gmail.comon 19 Jan 2013 at 8:24