Re: [Ekiga-list] Status of Win port
- From: Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] Status of Win port
- Date: Mon, 13 Apr 2009 17:50:47 +0200
Michael Rickmann wrote:
Am Montag, den 13.04.2009, 09:27 +0200 schrieb Eugen Dedu:
Michael Cronenworth wrote:
Eugen Dedu wrote:
"VFW support is still not visible even though ptlib is built with VFW
enabled." - I suppose this is still true...
Fails to register: Could you send us a -d 4 output? (I haven't seen
any, sorry)
Here's the -d4 output. I've also attached a "vfw" log in that I clicked
You have the same problem as Michael R.: STUN is not enabled and ekiga
tries to register through a private address, so you receive an error.
Let me think why STUN is not enabled in windows...
"Detect Devices" and the log shows what PTLib thinks of my system. You
can see "PTLIB/VideoForWindows" being output.
I do not know this kind of things. Snark, could you help here?
Currently, the STUN related sequence of events during win32 startup is:
1) notifiers from the config file are added (gmconf-glib.c)
2) notifiers are called via g_idle_add (gmconf-glib.c) including
disable_stun false
3) Opal::CallManager::start (opal-call-manager.cpp) finds stun_enabled
false and does not start the StunDetector.
4) ConfBridge::on_property_changed (opal-gmconf-bridge.cpp) calls
manager.set_stun_enabled to set stun_enabled.
I have attached a gdb log which shows this. It appears that enabling
stun comes to late for the CallManager which gives us only a single
chance for stun detection. The delay is probably caused by the glib idle
loop. I just found that taking out all the idle stuff from gmconf-glib.c
(see attached patch) lets me connect to ekiga.net. However, I do not
know the reason, why the notification was pushed in to the idle loop
originally.
It appears that the revision which introduced this error is
http://svn.gnome.org/viewvc/ekiga/trunk/lib/engine/components/opal/opal-call-manager.cpp?r1=7469&r2=7481,
is that right? If it is simple to you only, could you just revert that
revision and see the result?
--
Eugen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]