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
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
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
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
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
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
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
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
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
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
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 :
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
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
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 ?
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
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
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
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 [...]
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
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
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.
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
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
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.
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 :
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/
-
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
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
28 matches
Mail list logo
