Re: [Ekiga-list] Problems incoming calls.
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 ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Feature request: stop screensaver
Hi, I would like to know whether other people would be interested in adding a config flag to stop the screensaver during a video call. I wanted to try to add id myself I and I found that there is a call to reset the counter XResetScreensaver. I would like to ask the developers if there is an easy point in the code that is called often during a call. I would add later the relevant config option. Thanks Andrea ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
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? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout()
On Fri, Feb 13, 2009 at 5:55 PM, Michael Cronenworth wrote: > Ed wrote: > > Fedora 10 got all enthusiastic with SELinux maybe? > You might toggle SELinux in & out of permissive mode while you're in > flipin'-switches mode. > man setenforce & sestatus > ymmv > > > I'm using Ekiga 3.0.2 and Fedora 10 with SELinux in Enforced mode. I have no > issues. > > In fact, I haven't had a single SELinux related issue since Fedora 9. I've > been in enforced mode for almost a year now. If you do run into a problem > there is a graphical tool that notifies you of SELinux denials and offers > suggestions on workarounds. You can drop the SELinux jokes. I for one would love to hear some good SELinux jokes* ;) And i wouldn't suggest running without it - new tools etc make it very useful - especially with the new guide on the Fedora site. http://docs.fedoraproject.org/selinux-user-guide/ but in terms of "big & easy" diagnostic checks, aka flipin'-switches mode, it is up there with the firewall & rebooting. well maybe you can hold off on rebooting for a bit... And, like your local firewall, I wouldn't recommend running a system for very long without it Bas. (once you've got Ekiga working) sorry I couldn't help. *we have a LUG here and any new material is greatly appreciated ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
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. Will continue testing, googling etc. Again thanks for your help today and will report back once I find the cause. Bas. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
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. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
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). Thanks, Bas. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
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. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
On Sat, 2009-02-14 at 23:06 +1000, Bas Driessen wrote: > On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > > > Le samedi 14 février 2009 à 10:48 +1000, Bas Driessen a écrit : > > > Hello, > > > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > > account with my internet provider and I have setup Ekiga to use that > > > and that all works fine. However, within a couple of minutes, the > > > incoming calls do not work anymore. It goes straight to the voice > > > mail. If I de-register and register again, all works again for a > > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > > > What can be a possible cause and/or what can I do to further > > > investigate. To eliminate the fact that it is not a > > > router/infrastructure etc issue, I have tested with Twinkle. This > > > package seems stable both incoming as outgoing. So the issue appears > > > to be with Ekiga. > > > > > > How can I see how I am registered in Ekiga? I want to see something > > > like this: ;q=0.500;expires=360. As > > > outgoing calls still work, registration must perhaps get confused > > > somehow and change to something like: > > > ;q=0.500;expires=360 (I am only > > > guessing) meaning that I am still connected to a sip server, but not > > > linked anymore to the incoming number. > > > > > > Any ideas/tips/hints/solutions are appreciated. > > > > 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? > > Thanks again. > Can the following be an issue? It looks to me it is retrying something 3 times and then give up? (note, I have changed my real SIP number for a dummy number for obvious privacy reasons) 2009/02/14 23:57:15.447 10:59.032 Housekeeper:0x3ef66950 SIP Starting PUBLISH for offline retry 2009/02/14 23:57:15.447 10:59.032 Housekeeper:0x3ef66950 SIP Expiry time for PUBLISH set to 500 seconds. 2009/02/14 23:57:15.515 10:59.100 Housekeeper:0x3ef66950 SIP Transaction remote address is udp$203.2.134.1:5060 2009/02/14 23:57:15.515 10:59.100 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345...@sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$59.167.214.42:5060,if=192.168.1.14%br0 2009/02/14 23:57:15.516 10:59.101 Housekeeper:0x3ef66950 SIP Expiry time for PUBLISH set to 500 seconds. 2009/02/14 23:57:15.553 10:59.138 Housekeeper:0x3ef66950 SIP Transaction remote address is udp$203.2.134.1:5060 2009/02/14 23:57:15.553 10:59.138 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345...@sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 OpalUDP Binding to interface: 59.167.214.42:5060 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 SIP No Content-Length present from udp$203.2.134.1:5060, reading till end of datagram/stream. 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 SIP PDU 405 Method Not Allowed received: rem=udp$203.2.134.1:5060,local=udp $59.167.214.42:5060,if=192.168.1.14%br0 2009/02/14 23:57:15.593 10:59.178 Opal Liste...0x3ef25950 SIP Transaction 39 PUBLISH completed. 2009/02/14 23:57:15.593 10:59.178 Opal Liste...0x3ef25950 Opal Transport clean up on termination 2009/02/14 23:57:15.947 10:59.532 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 1 2009/02/14 23:57:15.948 10:59.533 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345...@sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:16.594 11:00.179 Housekeeper:0x3ef66950 SIP Set state Terminated_Success for transaction 39 PUBLISH 2009/02/14 23:57:16.947 11:00.532 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 2 2009/02/14 23:57:16.948 11:00.533 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345...@sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:18.948 11:02.533 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 3 2009
Re: [Ekiga-list] Problems incoming calls.
On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > Le samedi 14 février 2009 à 10:48 +1000, Bas Driessen a écrit : > > Hello, > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > account with my internet provider and I have setup Ekiga to use that > > and that all works fine. However, within a couple of minutes, the > > incoming calls do not work anymore. It goes straight to the voice > > mail. If I de-register and register again, all works again for a > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > What can be a possible cause and/or what can I do to further > > investigate. To eliminate the fact that it is not a > > router/infrastructure etc issue, I have tested with Twinkle. This > > package seems stable both incoming as outgoing. So the issue appears > > to be with Ekiga. > > > > How can I see how I am registered in Ekiga? I want to see something > > like this: ;q=0.500;expires=360. As > > outgoing calls still work, registration must perhaps get confused > > somehow and change to something like: > > ;q=0.500;expires=360 (I am only > > guessing) meaning that I am still connected to a sip server, but not > > linked anymore to the incoming number. > > > > Any ideas/tips/hints/solutions are appreciated. > > 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? Thanks again. Bas. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > Le samedi 14 février 2009 à 10:48 +1000, Bas Driessen a écrit : > > Hello, > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > account with my internet provider and I have setup Ekiga to use that > > and that all works fine. However, within a couple of minutes, the > > incoming calls do not work anymore. It goes straight to the voice > > mail. If I de-register and register again, all works again for a > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > What can be a possible cause and/or what can I do to further > > investigate. To eliminate the fact that it is not a > > router/infrastructure etc issue, I have tested with Twinkle. This > > package seems stable both incoming as outgoing. So the issue appears > > to be with Ekiga. > > > > How can I see how I am registered in Ekiga? I want to see something > > like this: ;q=0.500;expires=360. As > > outgoing calls still work, registration must perhaps get confused > > somehow and change to something like: > > ;q=0.500;expires=360 (I am only > > guessing) meaning that I am still connected to a sip server, but not > > linked anymore to the incoming number. > > > > Any ideas/tips/hints/solutions are appreciated. > > 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? Thanks again. Bas. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] ekiga 3 and 16bpp displays
Le vendredi 13 février 2009 à 18:35 +0100, Olivier Blin a écrit : > Hello, > > I have a crash with ekiga (3.0.x or 3.1.x) when using a 16bpp display. > Here is an interesting pointer in the trace: > Could not find visual with colordepth of 24 bits per pixel > > It seems that XWindow::checkDepth() fallbacks to 24bpp, but it does not > support 16bpp. > > The log + trace can be found here: > http://people.mandriva.com/~blino/ekiga-crash-16bpp.log > > Is ekiga supposed to work with only 24bpp and 32bpp displays? I think so yes. > What can be done to make it work on 16bpp displays? Fix the code so that it works with 16bpp too :-) But is 16bpp that common ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problems incoming calls.
Le samedi 14 février 2009 à 10:48 +1000, Bas Driessen a écrit : > Hello, > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > account with my internet provider and I have setup Ekiga to use that > and that all works fine. However, within a couple of minutes, the > incoming calls do not work anymore. It goes straight to the voice > mail. If I de-register and register again, all works again for a > minute or 2 and then same problem. Outgoing calls are fine and stable. > > What can be a possible cause and/or what can I do to further > investigate. To eliminate the fact that it is not a > router/infrastructure etc issue, I have tested with Twinkle. This > package seems stable both incoming as outgoing. So the issue appears > to be with Ekiga. > > How can I see how I am registered in Ekiga? I want to see something > like this: ;q=0.500;expires=360. As > outgoing calls still work, registration must perhaps get confused > somehow and change to something like: > ;q=0.500;expires=360 (I am only > guessing) meaning that I am still connected to a sip server, but not > linked anymore to the incoming number. > > Any ideas/tips/hints/solutions are appreciated. 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. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Dump FPS from ekiga 3.0.2 to a file
chaitanya mehandru wrote: Hi, Is there a way to record the FPS from ekiga and dump it to a file for taking an average FPS reading? I think the only solution is to modify the ekiga code yourself. -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
