Re: [Ekiga-devel-list] Ekiga-Engine and Interfaces for Ekiga
Damien Sandras has written: Are you sure what you need is not a softphone embedded in the webpage instead ? Indeed this would be the best solution but the possibility to use h.264 codec with ekiga is the maintainer to do it with ekiga. Further are there any interfaces, which I can use to develop my own application which communicates with the webservice for handle any call? We have very limited DBUS support, but it is possible to extend it. So in can use the ekiga engine to handle any calls and the webservice can control the engine over DBUS? And where can I get the ekiga engine? And is there the possibility to send the video stream to another sip address as the audio stream? (Video to a separate server which does the “RTP-to-Flash”? It is not possible currently, but SIP foresees this, so it is possible with some code. SIP has the ability if it would be expanded? Or is this a functionality of ekiga itself if anyone writes the functionality to the SIP-Client? To summarize : everything is possible, but you will need to code a bit. Indeed I need to code a lot :) Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Available Windows version of Ekiga.
Le mardi 14 octobre 2008 à 11:51 +0200, michel memeteau a écrit : Hi , just saw the Windows beta has been updated. After trugglilng with different software ( Xlite , qutecom ) in order to make my grand mother to use a webcam and Sip , I have to admit : Ekiga will become the easiest most popular SIp vidéo software on Windows as well . Xlite is to complexe , all other software have a technical problem etc ... Let's hope :-) Anyway right now , I can't retrive the last Build that has been posted on ekiga.org : http://www.ekiga.org/admin/downloads/latest/windows/windows/ekiga-setup-3.0.1beta-7205.exe , there is a probleme with the server it seems ? From here it works well. What problem do you have ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Available Windows version of Ekiga.
Hi , just saw the Windows beta has been updated. After trugglilng with different software ( Xlite , qutecom ) in order to make my grand mother to use a webcam and Sip , I have to admit : Ekiga will become the easiest most popular SIp vidéo software on Windows as well . Xlite is to complexe , all other software have a technical problem etc ... Anyway right now , I can't retrive the last Build that has been posted on ekiga.org : http://www.ekiga.org/admin/downloads/latest/windows/windows/ekiga-setup-3.0.1beta-7205.exe , there is a probleme with the server it seems ? the last one available before was the SVN 7144 http://snapshots.ekiga.net/snapshots/win32/archives/ thxs -- %---% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:[EMAIL PROTECTED][EMAIL PROTECTED] jabber/GoogleTalk : xmpp:[EMAIL PROTECTED] [EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Ekiga-Engine and Interfaces for Ekiga
Epelde Gorka a écrit : So, I've found that for a videoconference scenario, Ekiga is an interesting option. Right now, our platform is running on windows, so I'm interested in having a stable version of Ekiga for windows and having a working cross-building environment. We do already build ekiga for win32 by cross-building -- so the scripts should already be there (I'll let Matthias tell more about it). My idea was to start looking at DBUS, as is told in the previous email and looking at Ekiga's source code. My first effort would be to do some basic control and later on to be able to send rtp flows to other UI's and inserting external rtp flows from those UI's to Ekiga. Unfortunately, the engine doesn't control things down to the RTP streams... yet. Snark ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Ekiga-Engine and Interfaces for Ekiga
Hi all, I'm a researcher working on E-inclusion. I'm working on the Vital project ( http://www.ist-vital.org/). Our aim is to bring the latest technologies to people with disabilities (these can be elders or else). Our platform is based on URC technology (http://myurc.org/). Once that a profile called UI socket has been defined and a target adapter has been developed for it, this technology allows to control targets from any UI. So, I've found that for a videoconference scenario, Ekiga is an interesting option. Right now, our platform is running on windows, so I'm interested in having a stable version of Ekiga for windows and having a working cross-building environment. My idea was to start looking at DBUS, as is told in the previous email and looking at Ekiga's source code. My first effort would be to do some basic control and later on to be able to send rtp flows to other UI's and inserting external rtp flows from those UI's to Ekiga. Bests, Gorka Epelde 2008/10/14 Heiser Michael [EMAIL PROTECTED] Damien Sandras has written: Are you sure what you need is not a softphone embedded in the webpage instead ? Indeed this would be the best solution but the possibility to use h.264 codec with ekiga is the maintainer to do it with ekiga. Further are there any interfaces, which I can use to develop my own application which communicates with the webservice for handle any call? We have very limited DBUS support, but it is possible to extend it. So in can use the ekiga engine to handle any calls and the webservice can control the engine over DBUS? And where can I get the ekiga engine? And is there the possibility to send the video stream to another sip address as the audio stream? (Video to a separate server which does the RTP-to-Flash? It is not possible currently, but SIP foresees this, so it is possible with some code. SIP has the ability if it would be expanded? Or is this a functionality of ekiga itself if anyone writes the functionality to the SIP-Client? To summarize : everything is possible, but you will need to code a bit. Indeed I need to code a lot :) Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Available Windows version of Ekiga.
On Tue, Oct 14, 2008 at 8:06 PM, Damien Sandras [EMAIL PROTECTED]wrote: http://www.ekiga.org/admin/downloads/latest/windows/windows/ekiga-setup-3.0.1beta-7205.exe , there is a probleme with the server it seems ? From here it works well. What problem do you have ? Sorry, I was not really clear From my day location it was like 30 o/s and then dying , I tred several times. From my evening location it works really good. So maybe not a problem after all... ThX -- %---% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:[EMAIL PROTECTED][EMAIL PROTECTED] jabber/GoogleTalk : xmpp:[EMAIL PROTECTED] [EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-list] ekiga 3.0.0 win32 cross compile
Hi, Le mardi 14 octobre 2008 à 13:04 +0200, Epelde Gorka a écrit : Hi Damien, I'm having the same error as Jason. I would be interested in being able to compile Windows version so that I can test my own changes to Ekiga. Could you tell me where the problem is? Unfortunately, I have no idea :( -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Video
I am running ekiga 2.0.12 on Ubuntu8.04.1 with a P4 and 1GB of RAM. I have noticed that when I have Ekiga running and attempt to run a video with my browser, the video does not work until I kill Ekiga's video. Is there a way to avoid this? or must I just live with it?? Peaceed Edward Dunagin-Dunigan Bozeman, MT 59718 mobile 406-570-0992 Land line 406-556-7282 EKIGA: sip:[EMAIL PROTECTED] http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Connection issue = no audio/video calls
Damien Sandras ha scritto: Unfortunately, I fear nothing can be done : the port that STUN detects is not the real port being used by your router. I think SIP solutions are unusable with your provider :-/ A lot of people are using SIP with my provider with both phones and soft phones, it still sounds me there is a bug or a misconfiguration somewhere. For example I remember a few months ago I gave a try to wengophone, and it worked fine. Regards, Marco ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Connection issue = no audio/video calls
Le mardi 14 octobre 2008 à 22:40 +0200, Marco Chiappero a écrit : Damien Sandras ha scritto: Unfortunately, I fear nothing can be done : the port that STUN detects is not the real port being used by your router. I think SIP solutions are unusable with your provider :-/ A lot of people are using SIP with my provider with both phones and soft phones, it still sounds me there is a bug or a misconfiguration somewhere. For example I remember a few months ago I gave a try to wengophone, and it worked fine. Does it work better if you disable STUN support ? You can use : gconftool-2 -s /apps/ekiga/general/nat/stun_server --type=string to disable stun and gconftool-2 -u /apps/ekiga/general/nat/stun_server to reenable it. Perhaps they simply don't use stun at all ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Video
Le mardi 14 octobre 2008 à 14:39 -0600, Edward Dunagin a écrit : I am running ekiga 2.0.12 on Ubuntu8.04.1 with a P4 and 1GB of RAM. I have noticed that when I have Ekiga running and attempt to run a video with my browser, the video does not work until I kill Ekiga's video. Is there a way to avoid this? or must I just live with it?? It is not normal... -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] ekiga 3.0.0 win32 cross compile
Hi Damien, I'm having the same error as Jason. I would be interested in being able to compile Windows version so that I can test my own changes to Ekiga. Could you tell me where the problem is? Bests, Gorka Epelde 2008/9/30 Damien Sandras [EMAIL PROTECTED] Le mardi 30 septembre 2008 à 11:13 -0500, Jason Galyon a écrit : System: Ubuntu 8.04 Note, I updated my yasm to 0.7.1-0Ubuntu1 from the Intrepid repos (direct download and install from http://launchpadlibrarian.net/15979753/yasm_0.7.1-0ubuntu1_i386.deb x264 packages installed: libx264-57 1:0.svn2007122 libx264-dev1:0.svn2007122 x264 1:0.svn2007122 libx264.a(mc-c.o): In function `x264_hpel_filter_mmxext': /tmp/ekiga-3.0.0/win32/x264/common/x86/mc-c.c:219: undefined reference to `_x264_hpel_filter_v_mmxext' /tmp/ekiga-3.0.0/win32/x264/common/x86/mc-c.c:219: undefined reference to `_x264_hpel_filter_c_mmxext' /tmp/ekiga-3.0.0/win32/x264/common/x86/mc-c.c:219: undefined reference to `_x264_hpel_filter_h_mmxext' 3.0.1 will be released soon with WIN32 binaries. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ http://www.ekiga.org/v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] [EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Connection issue = no audio/video calls
-- Original Message -- From : Damien Sandras A lot of people are using SIP with my provider with both phones and soft phones [...] Perhaps they simply don't use stun at all ? They simply use different stun servers with Ekiga.net and/or other SIP providers/services, and sometimes they also use other SIP accounts without STUN support. We know that stun.ekiga.net - stun.voxgratia.org = IP Address 83.103.82.85 . Such IP Address belongs to a public subnet assigned from FASTWEB to a corporate customer, as You can check on RIPE Whois DB : == inetnum: 83.103.82.80 - 83.103.82.95 netname: FASTWEB-Reitek descr:Reitek public subnet country: IT admin-c: GC4384-RIPE tech-c: IRS2-RIPE status: ASSIGNED PA mnt-by: FASTWEB-MNT FASTWEB users mainly have a Hidden/Dynamic NAT M-1 connection towards Internet, but they don't have to go outside FASTWEB network in order to connect to stun.ekiga.net ;). Therefore stun.ekiga.net directly 'sees' the MAN private IP from which the packets are originated = it identifies such IP as an External one, even though the MAN IP Address is unreachable from Internet users (because of NAT Architecture). There isn't indeed any NAT between Marco's endpoint and the stun server = NAT socket creation fails Contact-Field always show the MAN IP as You can see from his logs : == Initial interface list: 127.0.0.1 [00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01] 00-00-00-00-00-00 (lo) 5.255.56.38 [fe:80:00:00:00:00:00:00:02:22:15:ff:fe:22:b9:8c] 00-22-15-22-B9-8C (eth0) [...] STUN server stun.ekiga.net replies Open NAT, external IP 5.255.56.38 [...] Cannot create socket using NAT type Open NAT Created bundled UDP socket 5.255.56.38:5060 [...] Contact: sip:[EMAIL PROTECTED]:5060;transport=udp Marco couldn't use STUN with his FASTWEB connection, but in such case he should have a client+service, that uses also the private/NAT addresses from which the IP packets are originated instead of that one supplied in the SIP protocol. If I'm not wrong, You are not doing so on Ekiga.net because it would only work with special numbers but not with other users, and so people would have the wrong impression that everything is setup correctly when it is not the case. Therefore I suggest that Marco should go on using his Ekiga.net account with STUN support, but with a different server = stun servers outside from FASTWEB network will 'see' his connections incoming from the NAT-R Public IP Address will recognize it as the external IP : == * http://www.voip-info.org/wiki/view/STUN - - stun.fwdnet.net (no XOR_MAPPED_ADDRESS support) - stun.ideasip.com (no XOR_MAPPED_ADDRESS support) - stun01.sipphone.com (no DNS SRV record) - stun.softjoys.com (no DNS SRV record) (no XOR_MAPPED_ADDRESS support) - stun.voipbuster.com (no DNS SRV record) (no XOR_MAPPED_ADDRESS) - stun.xten.com - stunserver.org - stun.sipgate.net:1 - numb.viagenie.ca (XOR_MAPPED_ADDRESS with rfc3489bis magic number ID) In case You should need it, this is the full-updated map of FASTWEB MAN Private IP Addresses = as You can see, FASTWEB is using (or better abusing) of Unallocated/Reserved IANA Ranges and also has some overlapping with Public Assigned/Allocated Ranges : == MAN Milano - IP 1.x.x.x MAN Milano Hinterland NORD - IP 2.x.x.x MAN Genova - IP 5.x.x.x MAN Trento/Veneto - IP 11.x.x.x - May 93 DoD Intel Information Systems MAN Milano Hinterland SUD - IP 14.x.x.x - Feb 08 switched from IANA PDN to IANA Reserved MAN Marche - IP 21.x.x.x - Jul 91 DDN-RVN MAN Grosseto - IP 22.x.x.x - May 93 Defense Information Systems Agency MAN Roma - IP 23.x.x.x MAN Toscana- IP 27.x.x.x MAN Biella/Torino - IP 28.x.x.x - Jul 92 DoD Network Information Center MAN Triveneto - IP 29.x.x.x - Jul 91 Defense Information Systems Agency MAN Bari - IP 31.x.x.x MAN Sicilia- IP 36.x.x.x MAN Bologna- IP 37.x.x.x MAN Napoli - IP 39.x.x.x MAN Torino - IP 41.x.x.x - Apr 05 AfriNIC (moving users to 28.x.x.x) MAN Reggio Emilia - IP 42.x.x.x MAN Sardegna - IP 51.x.x.x - Aug 95 Deparment of Social Security of UK -- |¯ \/¯ | /¯\ /¯__/¯__|| *FAX/Mail Server : +39 - 02700426582 | |¯|\/|¯|/¯_¯\|(__\__ \| *Casella Vocale : +39 - 0230312251 | |_| |_/_/ \_\___|___/| *FAQ ITGF http://plany.fasthosting.it | |-
Re: [Ekiga-list] ekiga doesn't work
Dear Michelle, first of all, I want to clarify that this email address is meant for trouble shooting with SIP addresses at ekiga.net, not for the Ekiga application itself, so for further assistance I suggest to ask the user mailinglists or even the developer mailinglists. However, I will try to give some useful answers that hopefully help a bit. WE DON'T. We have windows. We've downloaded everything. The current Ekiga for Windows packages (Ekiga 3.0.1 BETA) are snapshots from the development tree. They are tagged as Beta-software. However, what you described is not normal and not because it's Beta. Ekiga on Windows has problems, but communication is not one of these problems in general (if that would be the case, there would be no reason to make a Beta release). The latest Windows build is the revision 7205 uploaded yesterday and made accessible at http://wiki.ekiga.org/index.php/Windows_Users Again, keep in mind that the Windows version is in Beta stage and may have some surprises. Echo test never works from our end. We've tried several times. It's like we are not getting out. We see ourselves on the screen, but we can't get anything out. That usually indicates network issues. Ekiga uses a method to detect its own position compared to a public internet server (for example to detect blocking firewalls or NAT routers) called STUN. STUN should be able to detect the situation in about 95% of the common network setups in private area. It needs to detect that, because it has to tell its calling party (in your case the echo server) where to send the media data. It also may be a very restrictive firewall configuration, or a special type of NAT. Also some routers are able to actively support the SIP protocol - this confuses all the network tests Ekiga makes (naturally). Another possibility that makes it fail could of course be the local sound/video interface. In theory, Ekiga may not correctly use it. But since it uses common Windows interfaces to talk to the sound/video hardware, that shouldn't be the case. Also, since you mention that you see your own video locally, I don't think there's a problem. Do we have to use ekiga to communicate through video with my brother-in-law? What else can we use on our end and still communicate with brother-in-law who is using ekiga? Assumed he (and you) uses an account at the Ekiga.Net server, you're free to choose your client. Take a look at http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Windows which lists client-client interoperability. If you configure one of these programs to use the Ekiga.Net server, it should work. You may have the same media trouble with another program, in case you have a deeper network problem. Of course you're also free to choose the SIP service to use, Ekiga doesn't only work with Ekiga.Net, of course. But the servers work for about several thousand users, so I don't think that's the root case of a problem. I CC this answer to the Ekiga user mailinglist. You can subscribe to the list at http://mail.gnome.org/mailman/listinfo/ekiga-list Since you're not the only one who tries Ekiga on Windows systems, the chance is high somebody answers there (though it sounds like not being a Windows-specific problem, more like a problem that raises due to your network). Also there may be users who can suggest a Windows SIP software that works with Ekiga.Net from their expirience. -- This is my life - this is my net! - Jan ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
