On Sat, 2009-02-14 at 18:37 +0100, Damien Sandras wrote: > Le dimanche 15 février 2009 à 00:38 +1000, Bas Driessen a écrit : > > On Sat, 2009-02-14 at 15:17 +0100, Damien Sandras wrote: > > > Le dimanche 15 février 2009 à 00:07 +1000, Bas Driessen a écrit : > > > > On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > > > > > Le samedi 14 février 2009 à 23:26 +1000, Bas Driessen a écrit : > > > > > > > > > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > > > > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > > > > > > > > > Perhaps you could try sending a probe every 3 seconds. To change > > > > > > > this, > > > > > > > you can edit the following key : > > > > > > > /apps/ekiga/protocols/sip/binding_timeout > > > > > > > using gconftool or gconf-editor. > > > > > > > > > > > > > > Do not edit the config files manually, it won't work. > > > > > > > > > > > > Thanks Damien. Tried that, but it did not work unfortunately. > > > > > > Fedora > > > > > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > > > > > change. > > > > > > > > > > > > Is it possible that the problem is on the provider site? If so, > > > > > > which > > > > > > value/setting should I ask them to set/use? > > > > > > > > > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit > > > > > > STUN > > > > > > settings in Ekiga? Any other ideas? > > > > > > > > > > I think you should ask them. What you could do also is reconfigure > > > > > Ekiga > > > > > so that the registration timeout is set to 120 (2 minutes). That way, > > > > > it > > > > > will register every 2 minutes with your provider. It will hide the > > > > > problem. > > > > > > > > I just tried before setting it to 30 seconds. Same problem. (The > > > > default is 60 btw, which is still faster than the 120 you suggest). > > > > > > In that case, and if you are sure your modem is not the culprit, I > > > really suggest you to report a bug to your sip provider. > > > > Thanks for your help Damien. As mentioned before, Twinkle (SIP client) > > works OK and is stable with the same VoIP account on the same machine > > here. That is what makes me believe that this is an Ekiga issue. Have > > tried it from my Fedora laptop as well. Same results. Too bad ... > > Ekiga is so much better than the other VoIP clients, so that is why I > > am really desperate to get it to work. > > Are you using STUN in both cases?
Not sure how to set that in Ekiga. In older versions it was an option in the GUI somewhere. The only STUN reference I can see now is in gconf (/apps/ekiga/general/nat/stun_server) I left this at the default which is stun.ekiga.net. Do I leave that setting like that even though I am going through a different VoIP provider? Also what I want to find out today is if the issue has anything to do with the Fedora 10 64 bit build. I have had several 64 bit issues with other packages in the past on Fedora. I see that there is also a Windows version of Ekiga. I am going to install that on a Windows box here just to find out if it is a platform/distribution related issue. What I did find out since last posting is that the issue is not related to re-registering. Once incoming calls do not work anymore, even if I manually go to accounts de-register, register, incoming calls still do not work. I have to completely shutdown Ekiga and start it up again for it to work. Will post back results. Bas.
_______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
