This reminds me, also, Debian users can find v4 in "experimental" -- it
seems to solve a registration issue I'd been having with 3.2.7.
Mark
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
I want to keep on top of 4.0.0 to see how the wrinkles are getting
ironed out. (My current issue with the ekiga in Debian experimental is
that often when I receive a call, I hear the ringing, and I see a quick
flash of something, but I have nothing I can push to actually accept the
call!)
The snap
Eugen Dedu writes:
> On 17/02/13 10:29, Mark Carroll wrote:
>> I want to keep on top of 4.0.0 to see how the wrinkles are getting
>
> Glad to hear that! The current snapshot is from 11 02.
Oh! I was hoping for daily builds from the source code repository.
>> (My current
el_gallo_azul writes:
> Be aware that an Ekiga SIP account (a free ekiga.net one) can only be used to
> connect to another ekiga.net account.
Huh, that's interesting: when I am registered with iptel.org instead,
people with a free ekiga.net account can still call me.
Mark
_
I am having trouble with ekiga not registering when behind a BT Home
Hub running software version 8.1.H.U (Type A), whether or not I enable
network detection in the preferences. The -d 4 log is pasted at
http://pastebin.com/bd6kAWgp
In probing the port forwarding I set up, I discover that it is d
Still no luck, latest log in http://pastebin.com/fnmF8CY0 where I tried
configuring SIP to listen on 5050 instead: I hoped to be able to
initiate calls, but I can't even register with ekiga.net.
Basically, is it possible at all to use ekiga from behind NAT if UDP
5060 is blocked? (I have all the o
Stuart Gathman writes:
> You haven't established that the device is to blame. It could be your
> ISP blocking port 5060 (as some have infamously been know to do to
> promote their own VOIP solutions).
True. The device does support incoming 5060 for people who use the ISP's
VoIP service; I don
Obvious followup, though: if the ISP does firewall UDP 5060 upstream,
then is there any hope?
-- Mark
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
Eugen Dedu writes:
(snip)
> Are 5063 to 5060 blocked too or not?
All of UDP 5000 - 5100 are forwarded okay except for 5060.
(snip)
> So a good idea is to make ekiga use a port different than 5060, as
> written in previous e-mail.
Alas, it still fails if I try 5050, -d 4 at http://pastebin.com/
Thank you. I couldn't find any telnet access and in looking at its
configuration backup I don't recognize the kind of file at all. Among
the binary code in the file, some of the earliest strings are,
THENC
CANT-2BT Home Hub 2.0A
8.1.H.U
(so, model number, firmware version), but that's about as go
Eugen Dedu writes:
> An idea is to let registration be made even if it reports symmetric nat.
> In ekiga 4.0.1, in file
> lib/engine/components/opal/opal-call-manager.cpp, change at line 822:
>
> if (result == PSTUNClient::SymmetricNat
> || result == PSTUNClient::BlockedNat
>
Oh, but I should add -- with Ekiga 4.0.1 at the receiving end, I still
see the issue where for an incoming call nothing came up to let me pick
it up, it just told me afterward it had missed the call. Downgrading to
Ekiga 3.2.7 fixes that one. (Linux, with ctwm window manager.)
-- Mark
Eugen Dedu writes:
> On 07/09/13 18:36, Mark Carroll wrote:
>> Oh, but I should add -- with Ekiga 4.0.1 at the receiving end, I still
>> see the issue where for an incoming call nothing came up to let me pick
>> it up, it just told me afterward it had missed the call. Do
Eugen Dedu writes:
> Be sure that what you wrote is true, i.e. test for several executions of
> ekiga.
Ha, now I am getting the receiving call window just fine in 4.0.1. I am
playing around a bit with what other system libraries are installed but
that's probably irrelevant; if I see the problem
Stuart Gathman writes:
> Yes, this still happens to me. The problem is actually with the Desktop
> environment, not with Ekiga (other than refusing to provide an
> alternative to broken notifiers).
As I'm using a lightweight twm derivative, I am not sure I exactly have
a "Desktop environment"
Eugen Dedu writes:
> You are right: Ekiga does the right job, but notification programs are
> sometimes bad (do not show long strings), or notification server is bad
> (says it supports buttons, but it does not). So your request (to always
> show the call window) is good, I do not know what t
I am still trying to have a call work. Both sites are behind NAT with
the recommended ports forwarded, except that, from the caller, UDP 5060
can't be forwarded (though other ports can), so ekiga is configured to
use port 5050 instead, and is compiled with Eugen's hack to not just
give in when symm
Is there any other information I should provide to help? I could even
capture packets everywhere but the caller's router's WAN-side.
-- Mark
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
Thanks to Eugen we now have calling mostly working, except that there
are stability problems that seem very dependent on which codecs are
chosen, especially video codec. For instance, theora often freezes and
H264 lasts for maybe a minute before the call hangs up. I can even
completely crash Ekiga
I am trying to help remotely with difficulty registering. When I log
into the user's machine with ssh -CX and try running their ekiga it
registers okay for me, but quite often the local user seems to have some
kind of transport error reported. I got them to capture a log:
http://pastebin.com/xjhJN0
Eugen Dedu writes:
> On 05/03/14 21:25, Mark Carroll wrote:
>> I am trying to help remotely with difficulty registering. When I log
>> into the user's machine with ssh -CX and try running their ekiga it
>> registers okay for me, but quite often the local user see
Eugen Dedu writes:
> On 06/03/14 18:25, Mark Carroll wrote:
(snip)
>> Ah, thank you. It is interesting that it sometimes works, sometimes
>> doesn't, with it disabled. As I recall if I turn it on it always
>> complains that it can't detect the network. (This is
Porcelain Mouse writes:
> Recently, I tried using jitsi and, while jitsi registered an IPTEL
> account, it would not register the Ekiga account. Ekiga, on the other
> hand, cannot register the IPTEL account, either.
> User-Agent: Ekiga/4.0.1
I don't know how to interpret the log, I'm afraid,
23 matches
Mail list logo
