Hello Gadi,
> > You definitely did more work than necessary. A few notes: Story of my life :) > > 1. If you can use skype or some other soft phone app instead of ekiga at > the moment, I would encourage you to do so. Ekiga makes use of gconf, > and right now, the way we have local apps implemented, applications that > use gconf that run locally may trample over the gconf settings at the > same time as server-side gconf apps. Also, I know skype works well. I will check into using the skype soft phone tonight! Will it allow me to call on my local network by ip? All of my clients will only have access to the local network. > > 2. You should not have to add users or home directories to the chroot at > all. In fact, if you do, you may break things. When LOCAL_APPS is > enabled, the user's home directory is mounted on the client via sshfs, > and his/her user/group info is grabbed via ssh, as well, making the > client's environment match the server's environment. I read that the home directory was copied over via sshfs, but could not understand why ekiga could not "see" the client sound card and drivers. So I copied the the /home directory over to see if it made a difference and it did, so I just figured I had done something wrong in my setup. I will use skype and see how that works. > > 3. I am unclear from your description as to whether in the end, ekiga is > actually running successfully as a local app (ie on the client) or if it > is running on the server and pushed back to the client. If you run > "ltsp-localapps xterm", you can get an xterm within your session that is > running on the client and use that to check the client setup. Try > running "alsamixer -c0" to see if it picks up the sound card. Also, try > using "amixer -c0" instead of simply "amixer", as the default soundcard > may be the virtual pulseaudio soundcard rather than the physical sound > card. Ekiga was running as a local app because before I discovered that if it is running on the server and then started on the client without ltps-localapps, I got an error that port 5060 was already in use. Also, running under ltsp-localapps, I could communicate between the server and the client until the client session died; usually after the first, maybe second call. > > As always, drop into #ltsp on IRC to see if you can get some real-time > debugging help. Will do! Never been there before, read lots of archived sessions, and will probably be there this weekend working on this task. Regards, Murrah Boswell > > -Gadi > > On Thu, 2009-07-16 at 17:55 -0700, murrah boswell wrote: >> Hello all, >> >> I am running a kubuntu 9.04 testbed with ltsp and have installed ekiga sip >> phone in the chrooted environment. My lts.conf has >> LOCAL_APPS=Yes and LOCALDEV=Yes. >> >> When I initially booted a client and started ekiga with ltsp-localapps, >> there were no audio devices available to ekiga except >> SILENT. That is, it could not see my sound card on the client machine (Dell >> Latitude C600). So then I logged into kde on the server >> as my client user and started ekiga. Here I could see my sound card and the >> alsa drivers and got ekiga setup properly for that user >> on the server. Then I chrooted into /opt/ltsp/i386 and added the user that I >> wanted to use on the client side. Then after exiting >> from the chrooted environment, I copied the /home directory structure for >> that user into /opt/ltsp/i386/home and rebuilt the image. >> Then when I connect the client and logged in as the test user and started >> ekiga, I could see the alsa drivers that allowed me to >> setup ekiga on the client. With this configuration, I could make calls to >> and from the server and the client. However, then ekiga >> session on the client dies after one or two calls. Especially if the call is >> initiated from the server side. >> >> This is a pain and a lot of work, especially since I need to have about 100 >> thin clients connected with ekiga. If anyone has any >> clues about how I can get ekiga to recognize the client sound card and stay >> active, I would appreciate that information. >> >> Another problem is that amixer can not see the maestro3 drivers on the C600, >> so it does not function. Any ideas about that? >> >> I am also running a fedora 10 testbed, and have not been able to get ekiga >> to function period on the client. Anybody ever tried this >> and gotten it working? >> >> Regards, >> Murrah Boswell >> >> >> >> ------------------------------------------------------------------------------ >> 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
