On 09/10/2013 03:28 PM, David Ford wrote:
If there is no ideal solution - then perhaps a bad solution is the
best thing - pop the window up may not be elegant but it is the one
thing that does actually work.
What we have how is already a decent solution for broken notifiers. Just
click on the "
On 10/09/13 18:45, Mark Carroll wrote:
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
On 09/10/2013 04:20 PM, Eugen Dedu wrote:
On 10/09/13 21:54, Stuart Gathman wrote:
On 09/10/2013 03:28 PM, David Ford wrote:
If there is no ideal solution - then perhaps a bad solution is the
best thing - pop the window up may not be elegant but it is the one
thing that does actually work.
Wha
On 10/09/13 21:54, Stuart Gathman wrote:
On 09/10/2013 03:28 PM, David Ford wrote:
If there is no ideal solution - then perhaps a bad solution is the
best thing - pop the window up may not be elegant but it is the one
thing that does actually work.
What we have how is already a decent solution
I'll give it a try
David
On 10 September 2013 20:54, Stuart Gathman wrote:
> On 09/10/2013 03:28 PM, David Ford wrote:
>
>> If there is no ideal solution - then perhaps a bad solution is the best
>> thing - pop the window up may not be elegant but it is the one thing that
>> does actually work.
If there is no ideal solution - then perhaps a bad solution is the best
thing - pop the window up may not be elegant but it is the one thing that
does actually work.
David
On 10 September 2013 18:56, Eugen Dedu wrote:
> On 10/09/13 18:45, Mark Carroll wrote:
>
>> Eugen Dedu
>> >
>> writes:
>>
>
On 10/09/13 00:23, Stuart Gathman wrote:
On 09/08/2013 05:06 PM, Mark Carroll wrote:
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
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
On 07/09/13 18:34, Mark Carroll wrote:
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
On 09/08/2013 05:06 PM, Mark Carroll wrote:
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
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"
On 09/07/2013 12:36 PM, 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. Downgrading to
Ekiga 3.2.7 fixes that one. (Linux, wi
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
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. Downgrading to
>> Ekiga 3.2.
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. Downgrading to
Ekiga 3.2.7 fixes that one. (Linux, with ct
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:
> 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
>
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
This *could* be useful to get a complete firmware, but be very careful!
http://www.josephn.net/unlocking_bt_home_hub
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
Le 01/09/2013 19:05, *Mark Carroll* wrote:
I am having trouble with ekiga not registering when behind a BT Home
Hub running software version 8.1.H.U (Type A)
If BT means British Telecom, perhaps your "BT Home Hub" is really a
Technicolor/Thomson modem ? This kind of hardware needs specific set
On 06/09/13 13:10, Mark Carroll wrote:
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
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/
On 01/09/13 19:05, Mark Carroll wrote:
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
Both logs report symmet
On 05/09/13 21:42, gegetel wrote:
Le 01/09/2013 19:05, *Mark Carroll* wrote:
Is it possible to use Ekiga, at least to initiate SIP calls, if it is
behind NAT that won't forward 5060?
Using gconf-editor (apps > ekiga > protocols > sip), you can set
listen_port = 5061 and place and receive SIP
Le 01/09/2013 19:05, *Mark Carroll* wrote:
Is it possible to use Ekiga, at least to initiate SIP calls, if it is
behind NAT that won't forward 5060?
Using gconf-editor (apps > ekiga > protocols > sip), you can set listen_port
= 5061 and place and receive SIP calls as well. :-)
_
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
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
On 09/01/2013 01:05 PM, Mark Carroll wrote:
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
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
29 matches
Mail list logo
