Re: Two-party video conferencing
On Thu, 2010-01-07 at 17:54 -0500, Ben Scott wrote: Requirements: R1. Two parties only. (Not a big table meeting.) How is 2-party video conferencing different from Ekiga/Skype Internet phone calls with video? -- Lloyd Kvam Venix Corp DLSLUG/GNHLUG library http://dlslug.org/library.html http://www.librarything.com/catalog/dlslug http://www.librarything.com/rsshtml/recent/dlslug http://www.librarything.com/rss/recent/dlslug ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Two-party video conferencing
On Fri, Jan 8, 2010 at 10:36 AM, Lloyd Kvam pyt...@venix.com wrote: How is 2-party video conferencing different from Ekiga/Skype Internet phone calls with video? I have no idea. I've never worked with any kind of live video telecomm, other than a brief stint with MSN Messenger for another customer. Skype needs a third-party server, right? So that would be out. Ekiga, as you and Tom Buskey kindly suggested, looks like it might work. It's not explict in their FAQ, but it sounds to me like it might be able to work with an entirely internal system. Anyone know what's needed to make Ekiga work this way? I know what XMPP, SIP, Asterisk, etc., *are*, but I've never had to setup a working implementation. (I know we have consultants on this list. If someone has a canned solution ready, send me a proposal off-list. If the price is good I'll prolly just outsource the initial setup.) -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Video Conferencing
Hi All, Has anyone done any video conference work on Linux? My company purchased several Polycom systems for offices all over the world. However, only one of them allows for multiple (4) connections. I was wondering if there is a video conferencing server for Linux that would allow mulitple connections to tie more people together. Unfortunately, I know little to nothing about video conferencing technologies. I have found Gatekeepers, H.323 proxies, and a few other things, but I don't know what any of them are, and the docs are scarce. Any pointers? TIA, Kenny -- Tact is just *not* saying true stuff -- Cordelia Chase Kenneth E. Lussier Sr. Systems Administrator Zuken, USA PGP KeyID CB254DD0 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xCB254DD0 ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Video Conferencing
Kenneth E. Lussier [EMAIL PROTECTED] writes: Has anyone done any video conference work on Linux? My company purchased several Polycom systems for offices all over the world. However, only one of them allows for multiple (4) connections. I was wondering if there is a video conferencing server for Linux that would allow mulitple connections to tie more people together. Unfortunately, I know little to nothing about video conferencing technologies. I have found Gatekeepers, H.323 proxies, and a few other things, but I don't know what any of them are, and the docs are scarce. Any pointers? What you probably want is a H.323 Multiple Call Unit (MCU). I'd recommend checking out the stuff at http://www.openh323.org/ . Regards, --kevin -- Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA) cetaceannetworks.com!kclark (GnuPG ID: B280F24E) alumni.unh.edu!kdc ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Video Conferencing
On Fri, 2003-08-01 at 10:25, Kevin D. Clark wrote: I'd recommend checking out the stuff at http://www.openh323.org/ . A-HA! Thanks, Kevin. I was looking at their site, trying to figure out what was what. I'm going to download all of this stuff and see if I can get some of it to work. To make the long story short, H.323 is the standard that says 'this is how it's all done'. It's more then a protocol. Basically, here's the 'short' version. Set up an H.323 Gatekeeper. This software serves as kind of the directory service for things like address books, etc. When 'signing in', you'd sign in to the gatekeeper. When you wanted to make a call, the client would send a message to the gatekeeper saying 'I wanna call Ken', and the gatekeeper would 'set up' the call and provide the data to both client so they could connect. Mess around with any H.323 compliant clients. ANY client that is H.323 compliant, including netmeeting, will be able to use the above installed gatekeeper. Now, TECHNICALLY the gatekeeper isnt REQUIRED, however. I would STONGLY advise to use one. It makes administration and use MUCH easier, and would allow controls to be put in place.. A REALLY good 'What is H.323' can be found here: http://www.iec.org/online/tutorials/h323/index.html Note that H.323 isnt the only game out there. SIP provides virtually the same. H.323 is much better in a smaller environment, while SIP is more, hrm.. 'Large User Base' driven. However, the differences between H.323 and SIP are more in how they figure out who to call, request calls, setup things, etc.. In the end, call quality and the such is much more dependant on the codec and protocol used to carry the call.. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Video Conferencing
On Fri, 2003-08-01 at 14:43, Thomas Charron wrote: On Fri, 2003-08-01 at 10:25, Kevin D. Clark wrote: I'd recommend checking out the stuff at http://www.openh323.org/ . A-HA! Thanks, Kevin. I was looking at their site, trying to figure out what was what. I'm going to download all of this stuff and see if I can get some of it to work. Set up an H.323 Gatekeeper. This software serves as kind of the directory service for things like address books, etc. When 'signing in', you'd sign in to the gatekeeper. When you wanted to make a call, the client would send a message to the gatekeeper saying 'I wanna call Ken', and the gatekeeper would 'set up' the call and provide the data to both client so they could connect. So the gatekeeper is what does all of the connection handling, so to speak. Is the MCU part of the gatekeeper? This is where the documentation is lacking. There seem to be quite a few componants, no real explaination for what they are and what they do. They assume that if you're reading the doc, then you already know what you're doing. Bad assumption in my case ;-) Mess around with any H.323 compliant clients. ANY client that is H.323 compliant, including netmeeting, will be able to use the above installed gatekeeper. Now, TECHNICALLY the gatekeeper isnt REQUIRED, however. I would STONGLY advise to use one. It makes administration and use MUCH easier, and would allow controls to be put in place.. A REALLY good 'What is H.323' can be found here: http://www.iec.org/online/tutorials/h323/index.html Thanks for the linkage. I'll start reading Note that H.323 isnt the only game out there. SIP provides virtually the same. H.323 is much better in a smaller environment, while SIP is more, hrm.. 'Large User Base' driven. However, the differences between H.323 and SIP are more in how they figure out who to call, request calls, setup things, etc.. In the end, call quality and the such is much more dependant on the codec and protocol used to carry the call.. I thought that SIP was more used in the VoIP world. H.323 seems to be more standard in that most of the commercial equipment uses it, and most of the software packages (netmeeting, gnomemeeting, etc.) use it as well, allowing one to connect a small web cam up to a larger teleconferencing system. Thanks, Kenny ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss -- Tact is just *not* saying true stuff -- Cordelia Chase Kenneth E. Lussier Sr. Systems Administrator Zuken, USA PGP KeyID CB254DD0 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xCB254DD0 ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Video Conferencing
So the gatekeeper is what does all of the connection handling, so to speak. Is the MCU part of the gatekeeper? This is where the documentation is lacking. There seem to be quite a few componants, no real explaination for what they are and what they do. They assume that if you're reading the doc, then you already know what you're doing. Bad assumption in my case ;-) The MCU is the conferencing component. The gatekeeper is kinda like an LDAP server.. Kinda is VERY Kinda, it's simply a way to give you a general idea. It's for handling the translations of 'Kenny' to port xyz at comp1.g2.b3.mycompany.com. MCU is kinda like a, umm. Multiplexer.. And yea, I never really noticed it, but their docs are non existant.. I thought that SIP was more used in the VoIP world. H.323 seems to be more standard in that most of the commercial equipment uses it, and most of the software packages (netmeeting, gnomemeeting, etc.) use it as well, allowing one to connect a small web cam up to a larger teleconferencing system. Yes, SIP has taken off more in the voice side of things. But in the end, they're the same thing, just using a different codec. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
