Re: [Ekiga-list] What is 'ekiga's internal roster'?
All, FWIW, we use the term roster in XMPP to refer to a contact list. That's for that very reason it's named like that in ekiga ;-) FYI, roster has a specific meaning in English. It is a list that is rotated. So you put up a roster to operate a school canteen for example. Couple one does it on Monday couple two does it on tuesday etc. May I suggest that copying somebodies bad use of a word does not make it correct. Just me being pedantic, Brian -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] What is 'ekiga's internal roster'?
2009/1/7 Peter Saint-Andre stpe...@stpeter.im: Julien Puydt wrote: Peter Saint-Andre a écrit : FWIW, we use the term roster in XMPP to refer to a contact list. That's for that very reason it's named like that in ekiga ;-) Hmm, but Ekiga is not written just for XMPP developers is it? I think for consistency the working should be reconsidered. I have to add my agreement. XMPP and Ekiga have added a new definition for the word roster that didn't previously exist. One would have to have used XMPP and/or Ekiga, and done some research, in order to understand what they mean by roster. It's an inappropriate choice of word. Dave NICE CTI Systems UK Limited (NICE) is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] What is 'ekiga's internal roster'?
Duncan Lithgow a écrit : Hmm, but Ekiga is not written just for XMPP developers is it? I think for consistency the working should be reconsidered. The working has been reconsidered from 2.x to 3.x already : one of the goals of the new ekiga engine is to make it easier to support various protocols -- and XMPP is definitely a worthy protocol to support! Ekiga will support XMPP at some point in the future ; there are still a few things to clean up, but it's definitely almost possible. Snark on #ekiga ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
I cannot make SIP calls with Ekiga 3.0.1 on openSUSE 11.1. I was using, up until recently the 2.x releases of Ekiga, and they worked perfectly. I could connect to my VoIP provider and make calls. Ekiga 3.0.1 is another story though. I have cleared out all previous Ekiga config files, and gone through the setup wizard. I declined the ekiga.net SIP account because I already have a SIP account with my long standing VoIP provider. I have set up my SIP account, and Ekiga appears to be able to connect to it. I have triple checked the user name and password used to connect (the same SIP account I have used for several years with Ekiga and my VoIP provider). When I attempt to make a call to a landline (via my VoIP provider), all I seem to get is the message User is not available Ekiga is working (sound setup etc) because if I intentionally mis-dial and enter an invalid phone number I get a voice error message from my VoIP provider. I thought this might be a VoIP provider problem, but if I try Ekiga 2.12 from another Linux install it works fine... so it would appear to be directly linked to this version of Ekiga. Does anyone know what could be going wrong here and how I can fix it? C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Clayton wrote: I cannot make SIP calls with Ekiga 3.0.1 on openSUSE 11.1. I was using, up until recently the 2.x releases of Ekiga, and they worked perfectly. I could connect to my VoIP provider and make calls. Ekiga 3.0.1 is another story though. I have cleared out all previous Ekiga config files, and gone through the setup wizard. I declined the ekiga.net SIP account because I already have a SIP account with my long standing VoIP provider. I have set up my SIP account, and Ekiga appears to be able to connect to it. I have triple checked the user name and password used to connect (the same SIP account I have used for several years with Ekiga and my VoIP provider). When I attempt to make a call to a landline (via my VoIP provider), all I seem to get is the message User is not available Ekiga is working (sound setup etc) because if I intentionally mis-dial and enter an invalid phone number I get a voice error message from my VoIP provider. I thought this might be a VoIP provider problem, but if I try Ekiga 2.12 from another Linux install it works fine... so it would appear to be directly linked to this version of Ekiga. Please send the file 'output' after: ekiga -d 4 2output -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Clayton, I am currently running ekiga on opensuse 11.1 However, if you do a search of this list for posts from me you will see the issues I had. Two things spring to mind, one is you sy you declined the ekiga sip account, but did you remove the stun server as well? The other is that you are possibly running the wrong version. I would be interested to know(if you are a KDE user) if you managed to compile it. Thanks, Brian On Wed, 07 Jan 2009 21:51:42 +1000, Clayton smau...@gmail.com wrote: I cannot make SIP calls with Ekiga 3.0.1 on openSUSE 11.1. I was using, up until recently the 2.x releases of Ekiga, and they worked perfectly. I could connect to my VoIP provider and make calls. Ekiga 3.0.1 is another story though. I have cleared out all previous Ekiga config files, and gone through the setup wizard. I declined the ekiga.net SIP account because I already have a SIP account with my long standing VoIP provider. I have set up my SIP account, and Ekiga appears to be able to connect to it. I have triple checked the user name and password used to connect (the same SIP account I have used for several years with Ekiga and my VoIP provider). When I attempt to make a call to a landline (via my VoIP provider), all I seem to get is the message User is not available Ekiga is working (sound setup etc) because if I intentionally mis-dial and enter an invalid phone number I get a voice error message from my VoIP provider. I thought this might be a VoIP provider problem, but if I try Ekiga 2.12 from another Linux install it works fine... so it would appear to be directly linked to this version of Ekiga. Does anyone know what could be going wrong here and how I can fix it? C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Please send the file 'output' after: ekiga -d 4 2output Attached. I have been doing a little experimenting here, and rolled back to Ekiga 2.0.12 (from the openSUSE 11.0 repository) and did a few test calls to some landlines using my VoIP provider... and it worked fine... so I think this rules out the VoIP provider as the source of the problem. I then removed 2.0.12 and reinstalled 3.0.1 (from the openSUSE 11.1 repository) and tried to make the same calls to the same landlines, and all I get is the User is not available message. C. output.bz2 Description: BZip2 compressed data ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
I am currently running ekiga on opensuse 11.1 However, if you do a search of this list for posts from me you will see the issues I had. I did a quick search, and I fould messages from you about compiling... but nothing I read seem to link to the prob I'm encountering.. I might have missed something though Two things spring to mind, one is you sy you declined the ekiga sip account, but did you remove the stun server as well? In the 3.0.1 setup wizard, there is no step that details STUN server setup - not that I saw anyway. There are two steps for establishing an ekiga.net account for outgoing and incoming calls. Both steps have a checkbox at the bottom for skipping that step. The other is that you are possibly running the wrong version. The wrong version of what? Ekiga? It was/is the version released with openSUSE 11.1, and the build from the openSUSE repositories. If it's the wrong version, I would imagine that a lot of openSUSE users will be trying to use a broken build :-P i hope that's not the case here. I would be interested to know(if you are a KDE user) if you managed to compile it. Yes, I'm a KDE user... KDE4 to be sepcific. I haven't tried compiling Ekiga, or anything in openSUSE 11.1 yet. Just puling repo stuff for now. C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Le mercredi 07 janvier 2009 à 13:19 +0100, Clayton a écrit : Please send the file 'output' after: ekiga -d 4 2output Attached. Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] I have been doing a little experimenting here, and rolled back to Ekiga 2.0.12 (from the openSUSE 11.0 repository) and did a few test calls to some landlines using my VoIP provider... and it worked fine... so I think this rules out the VoIP provider as the source of the problem. I then removed 2.0.12 and reinstalled 3.0.1 (from the openSUSE 11.1 repository) and tried to make the same calls to the same landlines, and all I get is the User is not available message. C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en téléphonie IP / vidéoconférence ? sip:yann...@ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Clayton I did a quick search, and I fould messages from you about compiling... but nothing I read seem to link to the prob I'm encountering.. I might have missed something though One of the things you should have found is using gconf-editor to see if you do have the stun server set. While you are there you might want to have a look at your listening port and port range, if they are non standard. From your post I cannot tell, do you ever get registered? Two things spring to mind, one is you sy you declined the ekiga sip account, but did you remove the stun server as well? In the 3.0.1 setup wizard, there is no step that details STUN server setup - not that I saw anyway. There are two steps for establishing an ekiga.net account for outgoing and incoming calls. Both steps have a checkbox at the bottom for skipping that step. Agreed but it still may be worth checking. The other is that you are possibly running the wrong version. The wrong version of what? Ekiga? It was/is the version released with openSUSE 11.1, and the build from the openSUSE repositories. If it's the wrong version, I would imagine that a lot of openSUSE users will be trying to use a broken build :-P i hope that's not the case here. I did mean the wrong version of ekiga. I originally used the opensuse one and could not get my camera to work. I then switched to the rep-oss version and it all worked. To be fair I was trying a LOT of things at the time, so YMMV here. I would be interested to know(if you are a KDE user) if you managed to compile it. Yes, I'm a KDE user... KDE4 to be sepcific. I haven't tried compiling Ekiga, or anything in openSUSE 11.1 yet. Just puling repo stuff for now. Great, if you ever get around to compiling please post the result. I had no problem with PTLIB and OPAL, but could not get ekiga to go. Brian -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] eeepc and sony PCS-1600
Hello, i'm trying to test ekiga on eeepc with sony pcs-1600 system and i've got some problem i install ekiga with aptitude this is the Version : 2.0.12-1+nmu1 i launch ekiga, i try to connect on from my sony system : cf 1.txt i launch ekiga, i try to connect on my sony system from ekiga : same problem is there a solution ? thank you by advance -- --- Pascal Legrand *IUT de Chartres* - _Service Informatique_ --- 1, place Roger Joly 28000 Chartres Tel : 02 37 91 83 36 - Fax: 02 37 91 83 01 [r...@debian] ~ # ekiga [1] 5574 [r...@debian] ~ # *** glibc detected *** ekiga: free(): invalid next size (fast): 0x09dfa600 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb63bc6b4] /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb63be8b6] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb6594281] /usr/lib/libpt.so.1.10.10(_ZN13PAbstractList8RemoveAtEi+0x98)[0xb72fd598] /usr/lib/libpt.so.1.10.10(_ZN11PCollection9RemoveAllEv+0x20)[0xb72fbe50] /usr/lib/libopal.so.2.2(_ZN17Opal_YUV420P_H26113ConvertFramesERK13RTP_DataFrameR5PListIS0_E+0x40)[0xb6e505a0] /usr/lib/libopal.so.2.2(_ZN14OpalMediaPatch4Sink10WriteFrameER13RTP_DataFrame+0x48)[0xb692ef98] /usr/lib/libopal.so.2.2(_ZN14OpalMediaPatch4MainEv+0x1a5)[0xb6930ff5] /usr/lib/libpt.so.1.10.10(_ZN7PThread14PX_ThreadStartEPv+0xe3)[0xb72d6603] /lib/i686/cmov/libpthread.so.0[0xb65d04c0] /lib/i686/cmov/libc.so.6(clone+0x5e)[0xb642e61e] === Memory map: 08048000-08102000 r-xp 08:01 183078 /usr/bin/ekiga 08102000-08109000 rw-p 000ba000 08:01 183078 /usr/bin/ekiga 08109000-0810a000 rw-p 08109000 00:00 0 0980d000-09f17000 rw-p 0980d000 00:00 0 [heap] b307d000-b315d000 rw-p b307d000 00:00 0 b31f2000-b31f3000 ---p b31f2000 00:00 0 b31f3000-b3233000 rw-p b31f3000 00:00 0 b3233000-b3234000 ---p b3233000 00:00 0 b3234000-b32bf000 rw-p b3234000 00:00 0 b32bf000-b32c ---p b32bf000 00:00 0 b32c-b330 rw-p b32c 00:00 0 b330-b3301000 ---p b330 00:00 0 b3301000-b3341000 rw-p b3301000 00:00 0 b334c000-b3351000 rw-s 00:0d 5147 /dev/snd/pcmC0D0p b3351000-b3352000 rw-s 8100 00:0d 5147 /dev/snd/pcmC0D0p b3352000-b3353000 r--s 8000 00:0d 5147 /dev/snd/pcmC0D0p b3353000-b3358000 rw-s 00:0d 5154 /dev/snd/pcmC0D0c b3358000-b3359000 rw-s 8100 00:0d 5154 /dev/snd/pcmC0D0c b3359000-b335a000 r--s 8000 00:0d 5154 /dev/snd/pcmC0D0c b335a000-b335b000 ---p b335a000 00:00 0 b335b000-b339b000 rw-p b335b000 00:00 0 b339b000-b339c000 ---p b339b000 00:00 0 b339c000-b33dc000 rw-p b339c000 00:00 0 b33dc000-b33ee000 r--s 08:01 44013 /usr/share/mime/mime.cache b33ee000-b340 r--s 08:01 44013 /usr/share/mime/mime.cache b340-b3421000 rw-p b340 00:00 0 b3421000-b350 ---p b3421000 00:00 0 b351-b3528000 r--p 08:01 43643 /usr/share/locale/fr/LC_MESSAGES/evolution-data-server-2.22.mo b3528000-b352c000 r-xp 08:01 24228 /lib/i686/cmov/libnss_dns-2.7.so b352c000-b352e000 rw-p 3000 08:01 24228 /lib/i686/cmov/libnss_dns-2.7.so b352f000-b3536000 r--p 08:01 41429 /usr/share/locale/fr/LC_MESSAGES/gnome-vfs-2.0.mo b3536000-b363a000 rw-p b3536000 00:00 0 b363a000-b36b7000 r--p 08:01 26299 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Oblique.ttf b36b7000-b36b8000 ---p b36b7000 00:00 0 b36b8000-b36f8000 rw-p b36b8000 00:00 0 b36f8000-b36f9000 ---p b36f8000 00:00 0 b36f9000-b3739000 rw-p b36f9000 00:00 0 b3739000-b373a000 ---p b3739000 00:00 0 b373a000-b377a000 rw-p b373a000 00:00 0 b377a000-b377b000 ---p b377a000 00:00 0 b377b000-b3806000 rw-p b377b000 00:00 0 b3806000-b380c000 r-xp 08:01 40858 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so b380c000-b380d000 rw-p 5000 08:01 40858 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so b380d000-b381 r--p 08:01 41108 /usr/share/locale/fr/LC_MESSAGES/libbonoboui-2.0.mo b381-b3811000 ---p b381 00:00 0 b3811000-b3851000 rw-p b3811000 00:00 0 b3851000-b3852000 ---p b3851000 00:00 0 b3852000-b4052000 rw-p b3852000 00:00 0 b4052000-b4053000 r-xp 08:01 40861 /usr/lib/gtk-2.0/2.10.0/immodules/im-cedilla.so b4053000-b4054000 rw-p 08:01 40861 /usr/lib/gtk-2.0/2.10.0/immodules/im-cedilla.so b4054000-b4057000 r--p 08:01 43973 /usr/share/locale/fr/LC_MESSAGES/atk10.mo b4057000-b4058000 ---p b4057000 00:00 0 b4058000-b4858000 rw-p b4058000 00:00 0 b4858000-b4859000 ---p b4858000 00:00 0 b4859000-b5059000 rw-p b4859000 00:00 [1]+ Abandon ekiga [r...@debian] ~ # ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone number... the sip: and @provider was not required. C ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
can make a call now... the call quality is shockingly bad, but I do I enabled more audio codecs, and it's a lot better now (previously was using the defaults from the install) C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Le mercredi 07 janvier 2009 à 13:54 +0100, Clayton a écrit : I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone number... the sip: and @provider was not required. Indeed a good question. Damien ? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Clayton wrote: Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone Yes. I propose (maybe I will fix too): - either print Malformed number or something like this - or desactivate the Call button until the number has a @ inside -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Le mercredi 07 janvier 2009 à 14:11 +0100, Eugen Dedu a écrit : Clayton wrote: Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone Yes. I propose (maybe I will fix too): - either print Malformed number or something like this - or desactivate the Call button until the number has a @ inside In this particular case, there is only 1 account, thus ekiga could automatically add the full address by itself... That's more helpful - and, I suspect, a common case. Dave NICE CTI Systems UK Limited (NICE) is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone Yes. I propose (maybe I will fix too): - either print Malformed number or something like this - or desactivate the Call button until the number has a @ inside This seems like a major regression in functionality... doesn't it? Personally, I can type in the whole mess to make a call, but I am not the only user on this computer... there are other no-so-computer savvy users who use Ekiga to make calls. If I have to try to re-train them to type in a long and, to them, complicated URI to make a call, they will simply stop using it, or I will have to roll back to 2.0.12. C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Le mercredi 07 janvier 2009 à 14:11 +0100, Eugen Dedu a écrit : Clayton wrote: Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone Yes. I propose (maybe I will fix too): - either print Malformed number or something like this - or desactivate the Call button until the number has a @ inside In this particular case, there is only 1 account, thus ekiga could automatically add the full address by itself... ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
Clayton wrote: Try to call: sip:yournum...@sip.voiparound.com instead of sip:yournumber There is this error in your log: SIP Connecting to sip:[...] via [...] Socket Illegal RFC952 characters in DNS name [...] OpalCould not find host [...] OK, tried that (I thought I had tried that several times in the troubleshooting I had done before sending a mail to this list), and I can make a call now... the call quality is shockingly bad, but I do get through using the full sip:yournum...@sip.voiparound.com syntax. Is this a new requirement? In 2.0.12 I could simply type in the phone Yes. I propose (maybe I will fix too): - either print Malformed number or something like this - or desactivate the Call button until the number has a @ inside This seems like a major regression in functionality... doesn't it? I don't think so, because of the auto-completion feature (small combobox opened upon typing address). Personally, I can type in the whole mess to make a call, but I am not the only user on this computer... there are other no-so-computer savvy users who use Ekiga to make calls. If I have to try to re-train them to type in a long and, to them, complicated URI to make a call, they will simply stop using it, or I will have to roll back to 2.0.12. There is an auto-completion feature. Also, do you remember the old days when the e-mail addresses could contain only user names? Nowadays, the host name is mandatory... -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Cannot make SIP calls with Ekiga 3.0.1
This seems like a major regression in functionality... doesn't it? I don't think so, because of the auto-completion feature (small combobox opened upon typing address). But it's not auto completing where users expect it to... it's showing a long URI, but not filling in anything when you press Enter. To get the number to work you have to click the URI. Not intuitive or logical to the non-computer geek. It's also not remembering previously dialed numbers like 2.0.12 did. This is change in how Ekiga works definitely not newbie-user friendly. I just had my first What's wrong with the phone? question a few minutes ago. If I was not around they would have simply assumed Ekiga was broken... as I did an hour or so ago. This change has made Ekiga harder to use for the average user I deal with and support - particularly those who use Ekiga as the frontend for their VoIP provider. They are not using multiple accounts, and don't know or care about the SIP URI syntax. They want to type in a phone number and have it just work exactly as Ekiga 2.0.12 did... in fact this is one of the reasons I recommended 2.0.12 to so many people... it worked so well as a frontend to VoIP providers. There is an auto-completion feature. Also, do you remember the old days when the e-mail addresses could contain only user names? Nowadays, the host name is mandatory... Nope, I don't remember that. I started on the Internet (if you can call it that) in 1989. I had my first email address at the same time, and it was a n...@domain format. I couldn't do much with it except send messages within that domain, and then to CompuServe customers, but I had it... it was part of the services from one of the first serious BBS providers in the city I lived in. C. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Calling another voip provider
Hi all, How can I call a user of voip.com if I just have their username/sip name. Possible? Thanks. _ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/events.aspx___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): More observations about Ekiga 3.
peasth...@shaw.ca wrote: Damien, Previously, pe A call to sip:5...@ekiga.net works, ... If a call to a PSTN number through the Diamond service is attempted, the echo test repeats. The selected contact is ignored. ds A bit weird. you are probably not doing the right thing. Just verified these phenomena again this morning. Could you send us the gzipped output of ekiga -d 4 2output ? -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Re (2): Re (2): More observations about Ekiga 3.
Eugen Damien, Could you send us the gzipped output of ekiga -d 4 2output ? pe...@dalton:~$ ekiga -d 4 2output cannot open display: Run 'ekiga --help' to see a full list of available command line options. pe...@dalton:~$ The display must be identified properly. I've checked ekiga.man and do not see how it wants the display identified. Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): Re (2): More observations about Ekiga 3.
Le mercredi 07 janvier 2009 à 09:45 -0800, peasth...@shaw.ca a écrit : Eugen Damien, Could you send us the gzipped output of ekiga -d 4 2output ? pe...@dalton:~$ ekiga -d 4 2output cannot open display: Run 'ekiga --help' to see a full list of available command line options. pe...@dalton:~$ The display must be identified properly. I've checked ekiga.man and do not see how it wants the display identified. It is not something dependant on Ekiga, but on your Linux Desktop Environment If you can not start ekiga, chances are high that you can not start any program the same way. -- _ 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] eeepc and sony PCS-1600
Le mercredi 07 janvier 2009 à 13:49 +0100, Pascal Legrand a écrit : Hello, i'm trying to test ekiga on eeepc with sony pcs-1600 system and i've got some problem i install ekiga with aptitude this is the Version : 2.0.12-1+nmu1 i launch ekiga, i try to connect on from my sony system : cf 1.txt i launch ekiga, i try to connect on my sony system from ekiga : same problem is there a solution ? It looks very much like a broken installation with mismatched conflicting libraries installed on the system. -- _ 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
[Ekiga-list] Is ekiga supposed to detect oss4 devices
hi , Ekiga is not detecting my audio device . I use oss4 modules instead of alsa . Is that normal or there is something wrong with my setup ? System : Arch Linux Ekiga version : 3.0.1 Package Build details : http://repos.archlinux.org/viewvc.cgi/ekiga/repos/extra-i686/ - Nezmer nez...@gmail.com pgp9uFzI0PDk7.pgp Description: PGP signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Is ekiga supposed to detect oss4 devices
On Thu, 08 Jan 2009 00:05:24 +0100 yannick sev...@free.fr wrote: Le jeudi 08 janvier 2009 à 00:39 +0200, Nezmer a écrit : hi , Ekiga is not detecting my audio device . I use oss4 modules instead of alsa . Is that normal or there is something wrong with my setup ? AFAIK, there is no OSS4 support in PTLIB, thus ekiga won't work with those drivers. There is OSS (old) support. Maybe OSS4 have compatibility with the old OSS API? I see . That's really unfortunate . Ekiga is the 1st application not working for me with OSS4 . You can't have a perfect sound system in Linux , can you ? Well , enough trolling . Thank you for the fast reply . - Nezmer nez...@gmail.com pgplC7JHVeOzz.pgp Description: PGP signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] could not register : behind a router
Hi have the same problem. USRobotics 9108 with virtual server active: 5000-5100 and 3478-3479 UDP and TCP ekiga -d4 dyna.cxx(111)H264DYNASuccessfully loaded 'libavcodec.so.51' dyna.cxx(331)H264DYNASuccessfully loaded libavcodec library and verified functions h264pipe_unix.cxx(301)H264IPCPP: Found GPL process executable in /usr/lib/opal-3.4.2/codecs/video/h264_video_pwplugin_helper x264loader_unix.cxx(114)H264DYNATrying to open x264 library libx264.so.64 x264loader_unix.cxx(131)H264DYNASuccessfully loaded libx264.so.64 x264loader_unix.cxx(103)H264DYNALoader was compiled with x264 build 64 present x264loader_unix.cxx(106)H264DYNASuccessfully loaded libx264 library and verified functions h264pipe_unix.cxx(118)H264IPCPP: Successfully forked child process 14353 and established communication h264-x264.cxx(853)H264CodecEnabled 2009/01/08 02:07:29.460 0:00.127 ekiga Version 3.0.1 by on Unix Linux (2.6.27-11-generic-i686) at 2009/1/8 2:07:29.460 2009/01/08 02:07:29.461 0:00.128 ekiga Ekiga SVN revision: unknown 2009/01/08 02:07:29.463 0:00.130 ekiga Ekiga registered on D-Bus: org.ekiga.Ekiga 2009/01/08 02:07:29.465 0:00.132 ekiga PWLibFile handle high water mark set: 18 Thread unblock pipe 2009/01/08 02:07:29.466 0:00.133 ekiga PWLibThread high water mark set: 2 2009/01/08 02:07:29.466 0:00.133 ekiga PWLibFile handle high water mark set: 20 Thread unblock pipe 2009/01/08 02:07:29.466 0:00.133 ekiga PWLibThread high water mark set: 3 2009/01/08 02:07:29.466 0:00.133 ekiga PWLibFile handle high water mark set: 24 Thread unblock pipe 2009/01/08 02:07:29.468 0:00.135 ekiga PWLibFile handle high water mark set: 26 Thread unblock pipe 2009/01/08 02:07:29.470 0:00.137 ekiga PWLibThread high water mark set: 4 2009/01/08 02:07:29.471 0:00.138 ekiga HalManager_dbusInitialising HAL Manager 2009/01/08 02:07:29.475 0:00.142 ekiga HalManager_dbusPopulating device list 2009/01/08 02:07:29.479 0:00.147 ekiga HalManager_dbusDetected V4L capabilities on /dev/video0 name: Camera 2009/01/08 02:07:29.480 0:00.147 ekiga HalManager_dbusDetected V4L2 capabilities on /dev/video0 name: Camera 2009/01/08 02:07:29.667 0:00.334 ekiga HalManager_dbusPopulated device list with 13 devices 2009/01/08 02:07:29.668 0:00.335 ekiga HalManager_dbusPopulating interface list 2009/01/08 02:07:29.669 0:00.336 ekiga HalManager_dbusPopulating full interface list failed - Method getDevices with signature on interface org.freedesktop.NetworkManager doesn't exist 2009/01/08 02:07:29.862 0:00.529 ekiga Detecting V4L2 devices 2009/01/08 02:07:29.862 0:00.529 ekiga PV4L2Plugindetected device metadata at /sys/class/video4linux/ 2009/01/08 02:07:30.051 0:00.718 ekiga PWLibFile handle high water mark set: 31 Thread unblock pipe 2009/01/08 02:07:30.051 0:00.718 ekiga PWLibThread high water mark set: 5 2009/01/08 02:07:30.052 0:00.719 ekiga OpalManCreated manager. 2009/01/08 02:07:30.052 0:00.719 ekiga OpalManRegistered endpoint with prefix pc 2009/01/08 02:07:30.052 0:00.719 ekiga OpalEPCreated endpoint: pc 2009/01/08 02:07:30.906 0:01.573 ekiga PCSSCreated PC sound system endpoint. Players: Default EKIGA NVidia CK804 Recorders: Default EKIGA NVidia CK804 2009/01/08 02:07:30.906 0:01.573 ekiga OPALSetMediaFormatOrder() 2009/01/08 02:07:30.906 0:01.573 ekiga OPALSetMediaFormatMask() 2009/01/08 02:07:30.907 0:01.574 ekiga OpalManRegistered endpoint with prefix sip 2009/01/08 02:07:30.907 0:01.574 ekiga OpalEPCreated endpoint: sip 2009/01/08 02:07:30.907 0:01.574 ekiga PWLibFile handle high water mark set: 32 PUDPSocket 2009/01/08 02:07:30.908 0:01.575 ekiga IfaceMonInitial interface list: 127.0.0.1 00-00-00-00-00-00 (lo) 192.168.1.4 00-50-8D-7D-2C-ED (eth0) 2009/01/08 02:07:30.908 0:01.575 ekiga PWLibFile handle high water mark set: 33 Thread unblock pipe 2009/01/08
