Re: [Ekiga-devel-list] Call history
Julien Puydt a écrit : I committed preliminary call history code today. It won't make the contacts appear in the addressbook yet, but will print some data in the console. I committed more complete call history code today ; as far as I know, the last missing piece is correct status comments (the second line in the view). Snark ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Crash in accounts' code
Hi,
I was investigating the problems with gmconf-glib when I met this crash:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb45e7b90 (LWP 32657)]
GMAccountsEndpoint::Main (this=0x85f0e70) at
endpoints/accountshandler.cpp:131
131 if (accounts_iter-data) {
(gdb) bt
#0 GMAccountsEndpoint::Main (this=0x85f0e70)
at endpoints/accountshandler.cpp:131
#1 0xb733b7e4 in PThread::PX_ThreadStart ()
from /usr/lib/libpt_linux_x86_r.so.2.3-beta0
#2 0xb69294fb in start_thread () from /lib/i686/cmov/libpthread.so.0
#3 0xb6655d7e in clone () from /lib/i686/cmov/libc.so.6
While reading the code, I must admit I don't really understand how that
can be : there's a check on account_iter before doing the
account_iter-data.
What's strange is the next line :
list_account = GM_ACCOUNT (accounts_iter)-data;
where I would have expected :
list_account = GM_ACCOUNT (accounts_iter-data);
Does that looks interesting to someone?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-list] Can't Register into Blueface SIP Proxy
Le mercredi 02 avril 2008 à 20:40 +0200, Damien Sandras a écrit : Hi, Le mercredi 02 avril 2008 à 13:38 +0800, Elaine Xiong a écrit : Hi, all, Is there somebody using Ekiga to connect Blueface SIP service? Blueface is Ireland's first Broadband Phone Company. The website is www.blueface.com. I came across a register problem when I tried to connect the sip proxy. The result is that at most of time(99%) I can't register my account with Registering or Registration Failed messages showed in Ekiga. Actually I just got several times of register success at the very beginning. After that I'm not lucky any more. I can provide the logs of Ekiga and Xlite. With the latter one in windows I can register the same account into Blueface successfully and quickly. The log of Ekiga is from opensolaris and I got the same result from Linux(opensuse)/Windows. Just for your convenience , I list my account info below, User:testekiga Password:123456 Registar:sip.blueface.ie I did a few tests and I can register the account properly, but I am using plain SVN TRUNK (not 2.0.x). However, I see a potential bug that could be fixed. When we received the 1xx Trying, we should not send the REGISTER again. I'll change that in SVN TRUNK. Please test with it when you have the opportunity. Following Craig it is already behaving correctly. So it has probably been fixed recently. Can you try with TRUNK ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.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] details: Ekiga crash on Slackware 12.0
OK, I can now offer some specifics of my Ekiga 2.0.11 crash problem under Linux Slackware 12.0. I am trying to run Ekiga in KDE 3.5. Ekiga is from gsb-complete install (whatever version was current towards end of Jan 2008). Here are some details in chronological order. 1. Installed alsa-plugins-1.0.16 like this: patch -p1 alsa-pulse.patch ./configure make make install Rebooted/checked /usr/lib/alsa-lib. Updated files and links found. 2. Ran Ekiga offline. Got these two errors: --- error 1 - Error while starting the listener for the SIP protocol You will not be able to receive incoming SIP calls. Please check that no other program is already running on the port used by Ekiga. --- error 2 Same as above for H.323 - 3. Tried removing some modules: Removed following modules: bash-3.1# rmmod snd_seq_dummy bash-3.1# rmmod snd_seq_oss bash-3.1# rmmod snd_seq_midi_event bash-3.1# rmmod snd_seq bash-3.1# rmmod snd_seq_device bash-3.1# rmod snd_pcm_oss bash-3.1# rmmod snd_pcm_oss bash-3.1# rmmod snd_mixer_oss Still get the two above errors --- 4. Tested if this problem occurs while online. Launched Ekiga online, still the two errors pop up. I went ahead and tried to make a call. Ekiga crashed, giving this: --- error 3 -- bash-3.1# ekiga (ekiga:3305): GLib-GObject-WARNING **: gsignal.c:1715: handler `2912' of instance `0x849f980' is not blocked ekiga: pcm_params.c:2351: sndrv_pcm_hw_params: Assertion `err = 0' failed. Aborted bash-3.1# -- 5. Here is how my computer looks at time of crash: Here are modules at time of crash: bash-3.1# lsmod Module Size Used by ipv6 254496 14 lp 13736 0 parport_pc 27812 1 parport34632 2 lp,parport_pc psmouse39048 0 intel_agp 25116 1 agpgart31432 1 intel_agp evdev 11904 2 uhci_hcd 25612 0 Here is memory at time of crash: bash-3.1# ps -A PID TTY TIME CMD 1 ?00:00:01 init 2 ?00:00:00 migration/0 3 ?00:00:00 ksoftirqd/0 4 ?00:00:00 migration/1 5 ?00:00:00 ksoftirqd/1 6 ?00:00:00 events/0 7 ?00:00:00 events/1 8 ?00:00:00 khelper 9 ?00:00:00 kthread 58 ?00:00:00 kblockd/0 59 ?00:00:00 kblockd/1 60 ?00:00:00 kacpid 163 ?00:00:00 ata/0 164 ?00:00:00 ata/1 165 ?00:00:00 ata_aux 166 ?00:00:00 ksuspend_usbd 169 ?00:00:00 khubd 171 ?00:00:00 kseriod 172 ?00:00:00 kgameportd 198 ?00:00:00 pdflush 199 ?00:00:00 pdflush 200 ?00:00:00 kswapd0 201 ?00:00:00 aio/0 202 ?00:00:00 aio/1 345 ?00:00:00 scsi_tgtd/0 346 ?00:00:00 scsi_tgtd/1 351 ?00:00:00 scsi_eh_0 352 ?00:00:00 scsi_eh_1 392 ?00:00:00 kcryptd/0 393 ?00:00:00 kcryptd/1 482 ?00:00:00 udevd 1443 ?00:00:00 kpsmoused 1581 ?00:00:00 syslogd 1585 ?00:00:00 klogd 2023 ?00:00:00 inetd 2031 ?00:00:00 sshd 2039 ?00:00:00 acpid 2047 ?00:00:00 dbus-daemon 2052 ?00:00:00 hald 2053 ?00:00:00 hald-runner 2059 ?00:00:00 hald-addon-keyb 2060 ?00:00:00 hald-addon-keyb 2063 ?00:00:00 hald-addon-acpi 2065 ?00:00:00 hald-addon-stor 2081 ?00:00:00 crond 2083 ?00:00:00 atd 2127 ?00:00:00 gpm 2129 tty1 00:00:00 bash 2130 tty2 00:00:00 agetty 2131 tty3 00:00:00 agetty 2132 tty4 00:00:00 agetty 2133 tty5 00:00:00 agetty 2137 tty6 00:00:00 agetty 2218 ?00:00:00 gam_server 2387 tty1 00:00:00 startx 2403 tty1 00:00:00 xinit 2404 tty7 00:00:25 X 2408 tty1 00:00:00 sh 2409 tty1 00:00:00 startkde 2438 tty1 00:00:00 start_kdeinit 2439 ?00:00:00 kdeinit 2442 ?00:00:00 dcopserver 2444 ?00:00:00 klauncher 2446 ?00:00:00 kded 2451 tty1 00:00:00 kwrapper 2453 ?00:00:00 ksmserver 2454 ?00:00:01 kwin 2456 ?00:00:00 kdesktop 2458 ?00:00:01 kicker 2459 ?00:00:00 kio_file 2467 ?00:00:02 artsd 2470 ?00:00:00 kaccess 2472 ?00:00:00 kscd 2481 ?00:00:04 Terminal 2487 ?00:00:00 dbus-daemon 2488 ?00:00:00 dbus-launch 2490 ?00:00:00 gnome-pty-helpe 2491 pts/100:00:00 bash 2492 pts/200:00:00 bash 2493 ?00:00:00 knotify 2495 ?00:00:00 klipper 2497 ?00:00:00 korgac 2510 pts/200:00:00 gconfd-2 2512 ?00:00:00 bonobo-activati
Re: [Ekiga-list] details: Ekiga crash on Slackware 12.0
2. Ran Ekiga offline. Got these two errors: --- error 1 - Error while starting the listener for the SIP protocol You will not be able to receive incoming SIP calls. Please check that no other program is already running on the port used by Ekiga. --- error 2 Same as above for H.323 - This is the current normal behavior. Hmmm. This also happens when I am online, but I have successfully received incoming calls earlier. Should this error also pop up even when I am online, and also when Ekiga really can receive an incoming call? Dee _ More immediate than e-mail? Get instant access with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_instantaccess_042008___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] details: Ekiga crash on Slackware 12.0
Le jeudi 03 avril 2008 à 10:14 +, D Webb a écrit : From: [EMAIL PROTECTED] To: ekiga-list@gnome.org Date: Thu, 3 Apr 2008 11:45:04 +0200 Subject: Re: [Ekiga-list] details: Ekiga crash on Slackware 12.0 Le jeudi 03 avril 2008 à 09:34 +, D Webb a écrit : 2. Ran Ekiga offline. Got these two errors: --- error 1 - Error while starting the listener for the SIP protocol You will not be able to receive incoming SIP calls. Please check that no other program is already running on the port used by Ekiga. --- error 2 Same as above for H.323 - This is the current normal behavior. Hmmm. This also happens when I am online, but I have successfully received incoming calls earlier. Should this error also pop up even when I am online, and also when Ekiga really can receive an incoming call? When you are online, it should not happen. Are you sure you are running the GNOME version and not the experimental non GNOME version of Ekiga ? -- _ Damien Sandras For clarity, I could only have Ekiga (version is indicated as 2.0.11) on my box that comes with gnome-slackbuild that was released January 2008. Do you recommend I download/build/install your latest/greatest Ekiga version (2.0.12???) and try that instead? It won't change anything. But are you running a GNOME compilation of Ekiga or a non-GNOME compilation ? Please mail the output of ldd /usr/bin/ekiga so we can determine it. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.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-devel-list] Ekiga 3.00 available for WIN32 *only*
Stu, I have used [Skype] for 2 years very successfully. I had been forced into using Skype quite a number of times through the last years and I have some mixed experience with it. But that's not at all the point. The question is rather: Would you want to use a closed user group email system on which you can only write mails to people having an account on the same system and where you couldn't use your favorite MUA to read mail, but the only available option would be the closed source binary only specific OS platforms only mail client that comes with the service? I remember using two such systems back in the 80ies, one we may all remember, it was called CompuServe, the other one (for the Germans here) was BTX, the predecessor of T-Online. But 20 years have passed since then and even they pretty soon installed an Internet mail gateway to leverage Metcalfe's Law. They have been a bit slow when it comes to waiving their proprietary software and opening it up to POP3/IMAP/SMTP, though. Why are people so happy to leap back that 20 years when it comes to VoIP telephony? Comparing Skype to Ekiga (the software called Ekiga as opposed to the Ekiga.net SIP service) is comparing apples to pears. It's like comparing CompuServe to Thunderbird. I'argue that one of the reasons why Skype is as successful as it is the fact that VoIP telephone is still in it's infance. I know hardly anyone who is using Skype for serious business. (EBay's idea when buying them was just that, but it never materialized, AFAIK.) So as long as this is in the toy and novelty phase, fine. But nobody wants a monopoly, right? So we want competition. But how many different apps to you want to install onto your PC to make sure everybody else can reach you? How many contact IDs from different networks do you want to give out to people to be able to call you? Espeially given, that there is simple no need for these except to keep Skype Inc. and similar companies happy. Why? There are two universal addressing systems available to make an audio or video call to people. One was invented by the ITU a long time ago and is known as the world telephone numbering plan. The other one is known as a SIP address (that stuff which looks like an email address, i.e. sip:[EMAIL PROTECTED]). While SIP addresses are easier to memorize, they are somewhat hard to enter on classic phone devices (these gizmos with a 0-9 keypad), which is why a mapping from telephone numbers to SIP addresses makes sense. There is a well defined and accepted worldwide standard for this, known as ENUM. If I want to keep my contact details short, then all I need is a phone number and a SIP address which can be the same as I email address if I want to. Two things to remember for anyone who wants to contact me. And I can decide on which terminal device I will accept communication and I am free to switch my user agent if I feel a need for it. If I switch from Skype to Acme, I need to make sure everybody has the new contact details. And in Skype there isn't even anything like call forwarding. Consumer protection agencies together with telecom regulators in many parts of the world have fighted for years to enable portability of phone numbers as this is a prerequisite for serious competition among telcos (fixed and mobile). Why would we want to drop these achievements without any need? Coming back to the infancy of VoIP telephony: Don't mix up geeks and the rest of us. Skype looks successful, because a lot of people who have a PC have downloaded it once in their live. There is a ratio of downloaded copies versus users online of 10:1 or worse. And even if you take the some 2-digit million downloads of Skype, that would make for a market share in the single digit percents. No, not of the VoIP market, of the telephone calls market. Any medium sized european country will have more GSM subscribers than Skype worldwide. I can see a number of roadblocks for the further success of VoIP telephony: * Protocol fight. That SIP / H.323 / IAX2 thing is like the VHS / Beta or HD-DVD / BlueRay thing. Did SMTP / RFC822 ever have to seriously compete against any other protocols? I am very frustrated that often I can find a VoIP termination provider which is offering nice rates for a certain destination, but unfortunately, they don't speak my protocol. * The de-facto ENUM boycott. There is exactly one way to handle this IMO: Regulation. Period. Telco's don't want is, as they did not want number portability as they did not want a lot of other things. * Flatrates and the GSM revolution. I know a number of countries where people know fixed line phones just from old movies and laught at it. Where people still use landline phones, more often than not you can get a flatrate for unlimited national landline calls, for a bit more also national mobile networks or landlines on the same continent. The argument that VoIP is cheaper only work in niche situations
Re: [Ekiga-list] [Ekiga-devel-list] Ekiga 3.00 available for WIN32 *only*
Hi Torsten, I thought your comments were interesting. In fact I still have a COMPUSERV backup account. People select products for all sorts of reason, as for me provided a world wide network for my travels. I have used SKYPE for another reason equally as valid, cost reduction. Oh by the way, SKYPE call forwarding service works quite well both to my Offices and my Cell. The story of EKIGA is entirely another matter. One of clients wanted to look at LINUX basically for cost reduction in both hardware and software areas, stability and reliability. This revived some old memories, i.e. ATT V in the 80's, Red Hat 6 sometime in the early 90s and currently UBUNTU as server and Desktop products. Actually, I have been very surprised just how far the Linux industry has moved. UBUNTU 7.10 brought in EKIGA or one might say uncovered it from gnome. But many of the same old UNIX/LINUX problems some are good and some bad or hinder the commercial use of the application. UBUNTU has done a nice job bring it into an almost Windows competitive environment. SKYPE is excellent product so far, we're going to have wait for the Linux version. EKIGA has possibilities but attitude the general lack a central manual plus lack of stability is lacking. Red hat acquired many of these problems, i.e. I call the Windows problem, not mine go talk to the hardware or software manufacturer. My limited customer base and my personal thought have force me to judge multi-OS applications system,eg. OpenOffice vs Windows Office and Apache vs's MS XXX, and other things such as WiFI phones instead of cells? Nice talk. On Thu, 2008-04-03 at 16:40 +0200, Torsten Schlabach wrote: Stu, I have used [Skype] for 2 years very successfully. I had been forced into using Skype quite a number of times through the last years and I have some mixed experience with it. But that's not at all the point. The question is rather: Would you want to use a closed user group email system on which you can only write mails to people having an account on the same system and where you couldn't use your favorite MUA to read mail, but the only available option would be the closed source binary only specific OS platforms only mail client that comes with the service? I remember using two such systems back in the 80ies, one we may all remember, it was called CompuServe, the other one (for the Germans here) was BTX, the predecessor of T-Online. But 20 years have passed since then and even they pretty soon installed an Internet mail gateway to leverage Metcalfe's Law. They have been a bit slow when it comes to waiving their proprietary software and opening it up to POP3/IMAP/SMTP, though. Why are people so happy to leap back that 20 years when it comes to VoIP telephony? Comparing Skype to Ekiga (the software called Ekiga as opposed to the Ekiga.net SIP service) is comparing apples to pears. It's like comparing CompuServe to Thunderbird. I'argue that one of the reasons why Skype is as successful as it is the fact that VoIP telephone is still in it's infance. I know hardly anyone who is using Skype for serious business. (EBay's idea when buying them was just that, but it never materialized, AFAIK.) So as long as this is in the toy and novelty phase, fine. But nobody wants a monopoly, right? So we want competition. But how many different apps to you want to install onto your PC to make sure everybody else can reach you? How many contact IDs from different networks do you want to give out to people to be able to call you? Espeially given, that there is simple no need for these except to keep Skype Inc. and similar companies happy. Why? There are two universal addressing systems available to make an audio or video call to people. One was invented by the ITU a long time ago and is known as the world telephone numbering plan. The other one is known as a SIP address (that stuff which looks like an email address, i.e. sip:[EMAIL PROTECTED]). While SIP addresses are easier to memorize, they are somewhat hard to enter on classic phone devices (these gizmos with a 0-9 keypad), which is why a mapping from telephone numbers to SIP addresses makes sense. There is a well defined and accepted worldwide standard for this, known as ENUM. If I want to keep my contact details short, then all I need is a phone number and a SIP address which can be the same as I email address if I want to. Two things to remember for anyone who wants to contact me. And I can decide on which terminal device I will accept communication and I am free to switch my user agent if I feel a need for it. If I switch from Skype to Acme, I need to make sure everybody has the new contact details. And in Skype there isn't even anything like call forwarding. Consumer protection agencies together with telecom regulators in many parts of the world have fighted for years to enable portability of phone
