On Sun, Jan 10, 2010 at 3:41 PM, Rob Owens <row...@ptd.net> wrote: > On Sun, Jan 10, 2010 at 09:30:39AM -1000, R. Scott Belford wrote: >> On Sun, Jan 10, 2010 at 5:32 AM, Rob Owens <row...@ptd.net> wrote: >> > On Sun, Jan 10, 2010 at 12:32:09AM -0500, Rob Owens wrote: >> >> On Sat, Jan 09, 2010 at 11:04:42PM -0500, Rob Owens wrote: >> >> > On Tue, Jan 05, 2010 at 03:13:33AM -0700, David Burgess wrote: >> >> > > On Tue, Jan 5, 2010 at 12:50 AM, Ondrej Valousek <webs...@s3group.cz> >> >> > > wrote: >> >> > > > I do not think there is any workaround to this problem. >> >> > > > Actually it is the same problem as with running multiple NetMeeting >> >> > > > instances on Windows terminal server. >> >> > > > You can run multiple *client* instances, but only one server >> >> > > > instance. >> >> > > > I am not familiar with ekiga, but there should be an option whether >> >> > > > you >> >> > > > intend to use the server part of the application or not.... >> >> > > >> >> > > What about something like siproxd (http://siproxd.sourceforge.net)? >> >> > > I've never tried it, but it seems like if you could get multiple >> >> > > instances of ekiga to run, then point them to siproxd as a proxy... >> >> > > >> >> > I gave it a try today. Looks like it's intended to be installed on a >> >> > NAT firewall. I don't have one (just my router as a firewall). I tried >> >> > installing it on my single-nic LTSP server, but couldn't get it working. >> >> > In fact, some of the documentation indicates it might not work on a >> >> > single NIC machine: >> >> > >> >> <snip> >> >> >> >> I think I got it working. I'll do some more testing in the morning and >> >> provide updates for anybody following this thread. >> >> >> > Well, I got siproxd working on my LAN, but so far it doesn't allow me to >> > run multiple instances of Ekiga on the same machine. Each instance >> > wants ownership of port 5060 (and possibly other ports). The first >> > instance grabs those ports, and the other instances complain and won't >> > register. >> > >> > Still working on it... >> >> Aloha Rob >> >> I run siproxd on my pfsense gateway box. I use multiple SIP devices >> from my LAN including Ekiga clients and an iphone SIP client. I >> noticed this comment >> >> "ps. If you are using Ekiga behind pfsense/siproxd, you need to set >> the NAT traversal type to "None"." >> >> from here >> >> http://forum.pfsense.org/index.php?topic=10084.0 >> >> In reviewing my setups, I have all my devices set to use 5060 but I >> have them use a proxy at the LAN address of my siproxd/pfsense box. >> Ekiga's STUN server used to work, but, removing it and inserting my >> siproxd does fine. >> >> Before siproxd, I just set my SIP devices to 5060, 5061, etc. since my >> provider allows this. I'm happy to cross-reference any settings if it >> will help you in your quest. >> > Scott, I'd love to see some of your config files. I'm currently setting > each of my SIP devices to different ports, but that's a cumbersome > solution.
The tuning of my siproxd.conf file is done via the pfsense gui. My setup is pretty vanilla. I don't think this is your variable. > > Just to be clear, are you using multiple SIP devices on the same server? > If so, I'd like to see your siproxd.conf file. What OS are you running > your SIP devices on, and what version of Ekiga are you using? Are there > any client config changes besides turning off STUN and defining an > outbound proxy? My sip clients are not being launched from ltsp clients. I don't think that's a factor. To be exact, this is what is working for me. In my earlier post, I had not yet configured Ekiga to register two accounts simultaneously. - Ekiga 2.0.12 on a debian lenny eeepc install over my wireless lan through siproxd on pfsense works *without* nat settings and *without* setting outbound proxy manually. I currently have two lines terminated. - SIP Softphone 3.0 on the iphone works *without* setting outbound proxy. I can call the eeepc from the iphone, and vice versa. - Linksys/Cisco SPA 942 4-line phone works *with* setting outbound proxy to siproxd's IP. This device can call itself and the other devices. I provide my own SIP services, and as we speak I have 7 DID's assigned to 7 SIP accounts that I am registered to, through pfsense/siproxd, and all devices can call one another as well as in and out of the pbx to my att cell phone. Using freeswitch on your pfsense gateway is another option. I plan to change to this soon so that I can use the Speex codec across my wireless networks. I think your issue may be with tweaking and re-launching the ekiga client. It took me 4,324 attempts to get it 'right'. Let me figure out the best way to extract the siproxd.conf file, and I'll email it to you in private if you still need it. Running siproxd on a dual-nic machine seems to make it much easier > > Thanks a bunch. > > -Rob --scott ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _____________________________________________________________________ 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
