GNOME Bugzilla – Bug 118737
Improvements for better dial in compatibility
Last modified: 2006-03-08 19:04:03 UTC
Hi, At fist: I like gnomemeeting very much. Good work! Additional there are some features I'd like to have in the final version: START WITH KDE Works but brings up a annoying dialog: Cannot connect to LDAP server. This is normal when you have a dial up connection and start it. ADDRESSBOOK After that situation it is not possible to connect to the server in normal ways. I tried to reopen the addressbook, tried to disable/enable registration at userserver in preferences but it does not work. There is still something wrong. If you start gnomemeeting when you are connected everything is fine. GENERAL DIAL IN If you have a dial in connection it is quite normal that you disconnect from time to time. It would be a good feature to check the online state of the connection and reconnect to the server. How's about a connect/disconnect button to the server (or OFFLINE/ONLINE mode)? QUICK DISABLER FOR VIDEO I have been in a session and had problems with the sound. In that situation it would be a good feature if the Video main switch (on/off) would be close at hand...) Anyway I told you I like it and for .98 it is quite good!!! Wolfram
Hi, I have increased the severity because the described behavior is very annoying... Wolfram
Here are a few comments: ADDRESSBOOK What you are describing here is fixed in CVS (I think). GENERAL DIAL IN An offline/online mode is something I could implement, however it is far from trivial and I see no clear way to implement it correctly (or in a way I like) QUICK DISABLER FOR VIDEO You can already do that with 0.98. If you click on the last toolbar button (the one at the bottom) on the left, video transmission will be suspended. There is no way to disable video reception during a call for now, but you can ask to your remote partner to suspend his own video transmission. Any additional comments?
Hello, If Gnomemeeting handles the situation of being OFFLINE without error messages or hanging, I am glad without online/offline modes. But, with Offline/Online mode I meant to control the registration on the server only. I just want to tell Gnomemeeting when it makes sense to try to connect to the server and when not. Ideal would be if it can detect the dial-in state and does the login whenever connection is established. I hope I could express would I mean... Wolfram
Your problem can easily be fixed in 2 ways : - You write a script that is executed when your connection goes up or down and that changes the gconf key associated for the ILS registering - I add "profiles" support to the configuration system of GnomeMeeting. That way you could define a set of options for the situations where you are connected, not connected, or whatever... I feel that option 2 is the real fix, but due to the complexity, I doubt I'll be able to code that before 1.00.
Seems to become a real conversation :-) (I am at work and have no Gnomemeeting here, otherwise a reason to call...) To be honest, I know many things, but I am a beginner in the terms of Linux and Gnome. So the scripting will not come from me, I am afraid. Anyway, I am not realy sure that there is so much to change. If I am correct, my problem is the registration at the server. If I am not connected it fails and brings up the error message. Then, after a defined time it tries again. I think, all I need if a switch to enable a dial up mode. I mean, if the program cannot connect to the server then it accepts the situation (without popup) and retries periodically to connect again (maybe once a minute). When I am dialed in it will be able to log in and I am reachable. To get my dial out it should re-register myself within a shorter period (10 min?), if it is impossible it can go back to phase 1. A second solution would be a shortcut (button + menu entry) to login at server. So I would be able to connect if I want to. A third way could be to check for a specified device like ippp0 which is available (and has got an IP address) only if connected. Ok, I think I have consumed enough of your time. If you want me as a tester I am good enough. But I cannot help you with scripting I guess... Wolfram
hi again :) Unfortunately, this is more complex than what it looks like... Problems with dialup and the connection going up and down is not limited to ILS only, but it is also a problem for gatekeepers and such. So the solution needs to be clever and well-implemented... I'm sorry but I don't think I will be able to code that before 1.00...
Looks like something that could be solved with some dbus magic : - run a script when the connection goes up or down ; - the script can use dbus to instruct ekiga to register or unregister the accounts.
*** Bug 329071 has been marked as a duplicate of this bug. ***
All of this is now implemented in Ekiga 2.00 (when not obsoleted).