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
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
16 matches
Mail list logo