Slashdot Mirror
Get to Know GnomeMeeting
JigSaw writes "OSNews has a nice review/introduction to GnomeMeeting discussing its setup, usage and features. Some screenshots are included."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
50% of the time they won't answer your call
If you're wondering why, just look at what can greet you if you dare answer.
And the most important point of it all (from their FAQ):
2.2. Does it work with Netmeeting?
Yes, GnomeMeeting is compliant with all H.323 products, software and hardware.
At least the Windows users on the other end don't have to download any additional program, they can just continue to use what they did before...
Does this mean that all webcams will have to be pointed at a lower level and toward the garden. Gnomemeeting... Get it ...
Ok I'll get back to work .....
Stay tuned for new sig...
Have a look at the Gnome Meeting webpage; there are many more screenshots there with some preferences and other parts of the app shown that don't appear in the OSNews article. -- Steve
when will it communicate with Skype?
I'm a Windows user who wants to use it instead of NetMeeting??
...as reported by CPD.
Here's the report.
The Army reading list
I, for one, would like to welcome our new Gnome ..erm.. Underlords.
it could application share and or whiteboard with NetMeeting. I am sorry, but video conferencing is not novel, certainly not in 2003. Folks have been doing this since 1994 with CU-SeeMe, and vt et al. Cross paltform too, even before H.323.
The largest collection of use cases for NetMeeting involves *no* video, and a lot of application sharing/viewing. I think we all know this. What are the obstacles to getting some kind of linux based solution (please dont say vmware or wine!) that truly can interact with NM on a peer level?
... a decent non-geek screenshot of a multimedia application that makes me *want* to use it:
G no meMeeting_In_A_Call.png
http://www.gnomemeeting.org/screenshots/latest/
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
This is an exact quote of the last paragraph of the article mentioned! The post doesn't contain any news
I traded a few e-mails last year with Damien (the lead developer). He said a Windows port was being actively worked on and was just a few weeks/months off. Anyone heard anything on this? I was hoping to use GnomeMeeting in our office, where there's no chance of switching to Linux desktops anytime soon.
I know this might be scary but your could just get a firewall thats understands H323 realy this has little to do with the application it's just the standard way to get it accross the internet if your "firewall" (use that term loosly for those home nat products) dosent support the standard fix it. More advanced firewalls read into the h323 packets and dynamicaly open ports for the remote site only.
No sir I dont like it.
GnomeMeeting requires that you open no more than 17 ports for the "worst case" configuration.
= 0& faqpage=x269.html
If your firewall supports H.323 forwarding and you only want to make outbound calls, you're done.
Forward TCP port 1720 to your computer if you want to accept incomming calls.
If your gateway doesn't support H.323 forwarding:
Forward TCP port range [30000-30010]
Forward UDP port range [5000-5003]
99% of configurations are done here.
If you're using a gatekeeper, you must also forward UDP port range [5010-5013].
That's 17 ports in the worst case.
Here's the link in the FAQ.
http://www.gnomemeeting.org/index.php?rub=3&pos
The world will not get better through technology. We must seek to be better people.
Noticed that it doesn't work with macos X ichat. I noticed that during his introduction S jobs indicated ichat was built using opensource, so my question is how hard would it be to get it to work with ichat?
This is why Netmeeting and other H.323 solutions should be thrown on the trash heap.
In this day and age, the vast majority of people with high-speed connections are behind NATed DSL & cable routers. If your solution can't handle NAT, it is almost useless.
Right now, I consider Yahoo Messenger the only realistic solution. Sightspeed is nice as well, especially for higher-speed connectivity, but costly.
Try googling for H.323 freeware. Should be a point in the right direction. If the software is truly standards-based in nature then it should play well...
The best feature of gnomemeeting is that it supports 1394 AV/C cameras (aka DV camcorders). That means you can plug in you standard firewire camcorder and use that as your webcam! This requires a recent (and maybe customized) build, but it works quite well.
-molo
Using your sig line to advertise for friends is lame.
If your meeting software transforms your meeting into a multipoint tech support video conference, the software is not ready for primetime.
The software needs to be invisible - it can't impede the act of having the meeeting in any way. Currently no solution, including NetMeeting, truly achieves this goal.
There's also an answermachine available compatible with gnomemeeting/netmeeting available. You can find it here: http://www.openh323.org/code.html.
www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
I tried to get GNOMEMeeting a couple of years ago. Back then, my harddisk space was limited and I used Slackware. This means that I got to think twice before installing any software, because of the space constraints, and because of the effort in configuring, compiling and installing a package and every single dependency.
I had been able to get by without GNOME and KDE; most apps I used being GTK+ apps that could be compiled with or without GNOME. Not GNOMEMeeting. However, I figured that I could install the GNOME libraries and get not only GNOMEMeeting, but also some mighty cool features in my other apps...after all, there had to be a reason why people use the GNOME libraries, right?
Well, for some reason I don't remember I couldn't or wouldn't install GNOME from packages. So of I went to download, configure, compile and install every single component. Eventually I had a working GNOME install.
And then I got stuck...it turned out I also needed some libraries to support H.323, but couldn't get them compiled due to lack of virtual memory - I had 384 MB, which is exactly what the manual said I would need, but apparently was just not enough. Eventually I managed to compile the framework in debug mode - why this takes _less_ memory I still fail to see.
Compiling GNOMEMeeting was complicated by lots of errors apparently caused by the version of OpenH323 I had installed not being quite what GNOMEMeeting expected. Finally I managed to get everything installed and working...and then it turned out that GNOMEMeeting didn't work nearly as well as I had expected it to. In many cases, it just wouldn't connect. Judging from the article, not much has changed in that respect, although I am pleased to see that GM works with NAT now.
Now you may see the above as me blaming GM for Slackware lacking a good packaging system (mostly suffering from the lack of packages made for it), and that is indeed one source of the hardships I encountered. But I am asking you, and I seriously wonder, why does GM need GNOME? The way I see it, all it has to do is grab video and audio, encode it, and send it over the network, and play the video and audio it receives over the network. To my knowledge, none of these things require GNOME, nor are they easier to implement using GNOME. Am I wrong?
Please correct me if I got my facts wrong.