Hello Asmo,

Thanks for all your help with this!

Asmo Koskinen wrote:
> Asmo Koskinen kirjoitti:
> 
>> Well, Murmur is up now and I tested it with desktop fat machine:
> 
> So, I think if might work, but how to get very different kind of audio 
> hardware work as a microphone can be really hard/tricky..

I got linphone installed on both server and client before I read your emails. 
Linphone works except I am having trouble getting the 
microphone to work on the client side.

> 
> HP 2133 is thin client and I can run Mumble as a local application with 
> Zoom H2 as a USB mic (and Cheese as a local application with HP 2133's 
> webcam). I can hear thin client from desktop machine with Logitech USB 
> headset.

My testbed server is an old HP Pavilion a307x and my client is a Dell Latitude 
C600. Both of which are old technology, so I know I 
have some issues with recognition of hardware and drivers. For example, 
currently I can not get Fedora 10 + LTSP to configure the 
microphone on the C600 and the volume is very low. I have read about problems 
with microphones and volume control, so I will go 
searching for some solutions later today.

> 
> But I finish now here. Everything else is very easy to get work as a 
> local application - but voice/voip...
> 
> Btw - why voice/voip? Why not plain old text messages from 
> classroom/thin clients to another?

I will eventually be using fl_teachertool as soon as it is ported over to 
operating with sshfs in LTSP 5. My plan is to have a 
teacher who can monitor all the student clients and I want the teacher to be 
able to establish voice communicate with any one of the 
students. This way, if a student is having problems with a specific lesson, the 
teacher can call them and then take control of their 
  desktop to show them how to do something and communicate with during the 
session.

Also eventually, I will be limiting communication so the clients can only 
communicate with the server, i.e., the teacher. That is, I 
do not want the clients, in a class room environment, communicating with each 
other. I can probably do this with iptables running on 
the server or I may have to install a voip router on the server.

BTW, I have tried iTALC as a replacement for fl_teachertool, but have not been 
able to get it working. I will try again later after 
I get the voip issues resolved under Fedora 10 + ltsp. Then I have to do this 
all again with kubuntu 9.04 + kde3.5.

I will look further into Mumble/Murmur later today!

Regards,
Murrah Boswell

> 
> Go to to #ltsp, all the core developers are there all day long ;-) Ask 
> them what is possible in voip world.
> 
> Here is all the past discussion: http://www.nubae.com/logs/index.html
> 
> Best Regards Asmo Koskinen.
> 
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge  
> This is your chance to win up to $100,000 in prizes! For a limited time, 
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
> details at: http://p.sf.net/sfu/Challenge
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
> 

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to