I am running Ekiga 4.0.1 Linux box and, try as I might, I am unable to
get Ekiga to register to my Estreet SIP account. I have been able to
register to this account with other softphones in my Linux box (and
Android phone) , such as Zoiper and Linphone - but not with Ekiga.
When attempting to regis
Thanks for your reply. You are right in that as.estreet.com does not
resolve. However, using estreet.com does not fix the problem; it just
changes the error diagnostic to 'Could not register (Not found)'.
On Sat, Aug 2, 2014 at 2:23 PM, James Cloos wrote:
>>>>>> &quo
.227.111.13, but gives up
complaining that it has encountered a loop.
On Sat, Aug 2, 2014 at 3:33 PM, James Cloos wrote:
>>>>>> "JCA" == JCA <1.41...@gmail.com> writes:
>
> JCA> Thanks for your reply. You are right in that as.estreet.com does not
> JCA
I am trying to use Ekiga 2.0.9 under Slackware 12. The Ekiga
package is one delivered with Gnome Slacky 2.18.3, from www.slacky.eu.
So far I have noticed the following:
Most of the time, Ekiga crashes immediately after establishing a
connection with sip:[EMAIL PROTECTED] Sometimes the conn
least, I have yet to cause another crash.
This is of course terrific, but I wonder what is the difference? The
actual hardware is the same in both cases. Any ideas?
On 10/2/07, JCA <[EMAIL PROTECTED]> wrote:
> I am trying to use Ekiga 2.0.9 under Slackware 12. The Ekiga
> pa
> You probably hit yet another ALSA bug.
>
> You can test this :
> $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0
> -c 1 -r 8000 -f S16_LE -
>
> $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0
> -c 1 -r 16000 -f S16_LE -
They both seem to work fi
I am trying to dial a 1-800 number in the US using Ekiga and my
Ekiga PC-to-Phone account. When I do so, I get a recording to the
effect that such number is not free from my current location, and that
international calling fees will be charged if I proceed. This is kind
of galling, for I am call
>> I am trying to dial a 1-800 number in the US using Ekiga and my
>> Ekiga PC-to-Phone account. When I do so, I get a recording to the
>> effect that such number is not free from my current location, and that
>> international calling fees will be charged if I proceed. This is kind
>> of galling, f
>>> I am trying to dial a 1-800 number in the US using Ekiga and my
>>> Ekiga PC-to-Phone account. When I do so, I get a recording to the
>>> effect that such number is not free from my current location, and that
>>> international calling fees will be charged if I proceed. This is kind
>>> of galli
> I just tested those numbers:
> sip:[EMAIL PROTECTED] (codec GSM, Pizza Hut Telemarketing)
> sip:[EMAIL PROTECTED] Colonial Bank
> sip:[EMAIL PROTECTED] Society Of Former Special Agents Of Fbi
>
> They work here.
They do work all right for me as well.
> Not all numbers I tried do work, depen
> Le vendredi 12 octobre 2007 ? 20:43 +0200, yannick a ?crit :
>> Le vendredi 12 octobre 2007 ? 10:25 -0700, JCA a ?crit :
>> > test e.g. 1 800 4321359 (for Frontier Airlines.)
>>
>> It seems this number answer a SIP 407:
>> "407 Proxy Authentication Requ
> Skype has paid contracts with long-distance providers, ekiga.net
> relies on those available free-of-charge through the likes of
> freeworlddialup. I am expect Skype has leverage with one of its
> providers to properly terminate all 1-800 calls without charging you.
>
> If you register your copy
>> I hate to bring up the "S" word (it royally pisses me off when
>> Skype can do something that Ekiga can't) but the fact is that I have
>> yet to come across a single 1800 number in the US that Skype can't
>> reach at no charge. This without registering to anything other than
>> Skype.
>>
>>
> I don't understand why freeworlddialup doesn't have the muscle to keep
> the 1800 service going consistently. Unlike ekiga.net, it is based in
> the US. Perhaps they just have other fish to fry, or insufficient
> phone lines.
>
> Therefore my advice would be - if you are in the US, get Asterisk
I have upgraded to Ekiga 3.0 and, much to my dismay, the info I
had in my address book is gone. I still have the names, but not the
phone numbers. Are they really gone for good, or can they be at all
retrieved?
___
ekiga-list mailing list
ekiga-lis
> Le jeudi 25 septembre 2008 ? 11:27 -0600, JCA a ?crit :
>> I have upgraded to Ekiga 3.0 and, much to my dismay, the info I
>> had in my address book is gone. I still have the names, but not the
>> phone numbers. Are they really gone for good, or can they be at all
>>
> Le samedi 27 septembre 2008 ? 08:03 -0600, JCA a ?crit :
>> > Le jeudi 25 septembre 2008 ? 11:27 -0600, JCA a ?crit :
>> >> I have upgraded to Ekiga 3.0 and, much to my dismay, the info I
>> >> had in my address book is gone. I still have the names, but n
> Le samedi 27 septembre 2008 ? 17:00 -0600, JCA a ?crit :
>
> [...]
>
>> >
>> > The only different thing is that they are not displayed by default, you
>> > have to right-click...
>>
>> Right-click where? When I do so on some entry in the
OK, here is my problem:
I am running Ekiga 2.0.3 on a Linux box under a 2.6.19.1 kernel.
My ADSL line does 330 KB/s downstream, 50 KB/s upstream. I am behind a
firewall that Ekiga detects as Port Restricted NAT, so I have enabled
STUN support, because my modem does not support SIP or H.323
ALSA version seems to be 1.0.13
On 1/11/07, JCA <[EMAIL PROTECTED]> wrote:
> OK, here is my problem:
>
> I am running Ekiga 2.0.3 on a Linux box under a 2.6.19.1 kernel.
> My ADSL line does 330 KB/s downstream, 50 KB/s upstream. I am behind a
> firewall that
>>My ADSL line does 330 KB/s downstream, 50 KB/s upstream.
>
> Do You mean 50k BITS or 50k BYTES?
That would be 50 kibibytes/s = 50*1024*8 bits/s.
> I notice that Ekiga selects the PCMA audio codec.
> If 50kbits it is not enough for PCMA. Try other codec with other echo
> test: ex: [EMAIL P
>> The only thing I am getting is a "Remote user rejected call" error message.
>>
>>
> 1). Are You sure, You have iLBC codec enabled? (don't remember if that
> site accepts anything else).
That's right - iLBC was not enabled. After enabling it, the
results were the same as when getting a con
>> That's right - iLBC was not enabled. After enabling it, the
>> results were the same as when getting a connection with [EMAIL PROTECTED]
>> and the PCMA codec - sound so choppy that is almost unintelligible.
>
> Are you using ALSA for both your input and output devices? There is a
> problem
> What speed are you connected to the internet?
300 KB/s downstream, 50 KB/s upstream, where 1 KB = 1,024 bytes.
GnomeMeeting 1.2.2 used to work fine on this connection, and so
does Skype (well, as fine as Skype can work).
___
ekiga-list mailing l
> > What speed are you connected to the internet?
>
>300 KB/s downstream, 50 KB/s upstream, where 1 KB = 1,024 bytes.
>
>GnomeMeeting 1.2.2 used to work fine on this connection, and so
> does Skype (well, as fine as Skype can work).
>
> Then most probably your ALSA setup has changed, becaus
> Are you using video when you make your calls?
No.
> I'm not sure if I asked you before, but you might try using GSM instead
> of ilbc if your VOIP provider uses it.
Tried, no change.
> Also if your VOIP provider uses SPEEX narrow, that will help a lot too.
> I'm using cable (1 megabyte
Before thinking of spreading Ekiga, might it not be better first to
a) make it totally independent of Gnome, and b) get it to work at
least as solidly as its competitors? Quite simply, these two are the
only reasons why I can't get my organization to move to Ekiga, instead
of the current Skype/G
> a) you can compile it with --disable-gnome
I will try that. The point is, this should be the default.
> b) you should report all problems you encounter, Ekiga 2.0.x is quite
> stable for most users...
I have reported my problems, and so far they remain unsolved. The
fact remains that un
> Have you tried with Ekiga 2.0.5 ?
pwlib 1.10.4, configured with
./configure --prefix=/usr --enable-plugins --disable-oss --enable-v4l2
refuses to compile on my Slackware 11.0 box:
make[3]: Entering directory `/home/IJK/pwlib-1.10.4/plugins/vidinput_v4l2'
mkdir -p ../pwlib/device/videoinput
A while ago I reported severe sound problems in version 2.0.3 when
interacting with sip:[EMAIL PROTECTED] - the echoed sound was so choppy
that Ekiga was, for all practical purposes, unusable.
I have just tested with version 2.0.5. The first was perfect: The
voice from came through with per
30 matches
Mail list logo
