Hello,
when will be the ZRTP function released? Is where any hope, to get this
important function?
Daniel Smertnig has been working on ZRTP support. This was also part of
the Google SoC propositions, but unfortunately, it got rejected. I think
that some people do not understand the importance of
Le mardi 30 décembre 2008 à 12:00 +0100, Palo S. a écrit :
I have reproduced the same problem on yet another computer
running Ubuntu with Ekiga 3.0 packaged by Yannick. So my
suspicion on distribution specificity is wrong. I am even
more wondering why nobody else complains about this...
Le mardi 30 décembre 2008 à 12:00 +0100, Palo S. a écrit :
I have reproduced the same problem on yet another computer
running Ubuntu with Ekiga 3.0 packaged by Yannick. So my
suspicion on distribution specificity is wrong. I am even
more wondering why nobody else complains about this...
- Originálna Správa -
Od: yannick
Komu: Ekiga mailing list
Poslaná: 30.12.2008 12:40
Predmet: Re: [Ekiga-list] 473 Filtered destination
Le mardi 30 dĂŠcembre 2008 Ă 12:00 +0100, Palo S. a ĂŠcrit :
I have reproduced the same problem on yet another computer
running Ubuntu
Can you try to remove from your contact list all things related to
ekiga.net : 5...@ekiga.net, 5...@ekiga.net and so on ?
You can keep your normal contacts.
Looks like a good shot! Running for two hours now and
still ok. Also the amount of traffic is much smaller.
The log is 400k now
- Originálna Správa -
Od: Damien Sandras
Komu: Ekiga mailing list
Poslaná: 30.12.2008 15:20
Predmet: Re: [Ekiga-list] 473 Filtered destination
Le mardi 30 dĂŠcembre 2008 Ă 15:20 +0100, Palo S. a ĂŠcrit :
Can you try to remove from your contact list all things related
Le dimanche 28 décembre 2008 à 20:36 +0100, Palo S. a écrit :
Does TRUNK give the same problem ?
TRUNK gives the same problem. Furthermore I reproduced
the same problem on two other computers: one in the same
LAN and one in completely different network environment.
I still see SUBSCRIBE and NOTIFY and responses being exchanged. Only the
REGISTER seems to be blocked or am I missing something ?
SUBSCRIBE and NOTIFY are only exchanged for a few minutes:
21:17:48 last REGISTER (expires 600)
21:22:46 last SUBSCRIBE (expires 300)
and then absolutely nothing
Le lundi 29 décembre 2008 à 13:36 +0100, Palo S. a écrit :
I still see SUBSCRIBE and NOTIFY and responses being exchanged. Only the
REGISTER seems to be blocked or am I missing something ?
SUBSCRIBE and NOTIFY are only exchanged for a few minutes:
21:17:48 last REGISTER (expires 600)
Does TRUNK give the same problem ?
TRUNK gives the same problem. Furthermore I reproduced
the same problem on two other computers: one in the same
LAN and one in completely different network environment.
Palo
__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu
Does TRUNK give the same problem ?
TRUNK gives the same problem. Furthermore I reproduced
the same problem on two other computers: one in the same
LAN and one in completely different network environment.
Are you talking about the REGISTER not being refreshed ?
Yes
Le samedi 27 décembre 2008 à 00:06 +0100, Palo S. a écrit :
I set it to 3600 in gconf
(sip:registrar_registration_timeout as well as in
accounts_list) but it seems that both settings are
ignored? The log still says 36000. Is there a
separate settings at ekiga.net? Is there a way
for
Le samedi 27 décembre 2008 à 00:06 +0100, Palo S. a écrit :
I set it to 3600 in gconf
(sip:registrar_registration_timeout as well as in
accounts_list) but it seems that both settings are
ignored? The log still says 36000. Is there a
separate settings at ekiga.net? Is there a way
for
Does TRUNK give the same problem ?
The latest TRUNK segfaults right after start.
Valgrind says
==27759== Invalid read of size 4
==27759==at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager,
Le samedi 27 décembre 2008 à 16:56 +0100, Palo S. a écrit :
Does TRUNK give the same problem ?
The latest TRUNK segfaults right after start.
Valgrind says
==27759== Invalid read of size 4
==27759==at
Le jeudi 25 décembre 2008 à 16:13 +0100, Palo S. a écrit :
Offline is sent back when the user is not in the database anymore.
Perhaps it did not refresh the registration in time ? That is something
you should look in his log : is there a REGISTER request to renew the
registration or
Le vendredi 26 décembre 2008 à 03:05 +0100, Palo S. a écrit :
I don\\\'t know whether this is related to the issue we
have in this thread...
Now I know - it is related. It seems to be a pattern:
After some time (seems to be around 1-2 hours from Ekiga
start) there is no
The complete log is here:
ftp://quacka.no-ip.org/pub/ekiga-problem.log
There is no call at the end I tried to close
Ekiga and then had to kill it. (I also tried to
call to the client but there is nothing about
it in the log, the server returned 408 Request
Timeout.)
Palo
__
Le vendredi 26 décembre 2008 à 12:01 +0100, Palo S. a écrit :
The complete log is here:
ftp://quacka.no-ip.org/pub/ekiga-problem.log
There is no call at the end I tried to close
Ekiga and then had to kill it. (I also tried to
call to the client but there is nothing about
it in the log, the
Le vendredi 26 décembre 2008 à 12:27 +0100, Damien Sandras a écrit :
Le vendredi 26 décembre 2008 à 12:01 +0100, Palo S. a écrit :
The complete log is here:
ftp://quacka.no-ip.org/pub/ekiga-problem.log
There is no call at the end I tried to close
Ekiga and then had to kill it. (I also
You set the registration time to 36 000 seconds in the account
definition. It means 10 hours.
I can\'t remember setting that but it is so indeed...
I have limited it to 20 minutes max and 10 minutes min at
the Ekiga.net level = it should not accept 10 hours anymore.
Did not help, still
I will set it to 3600 in the client and we shall see...
I set it to 3600 in gconf
(sip:registrar_registration_timeout as well as in
accounts_list) but it seems that both settings are
ignored? The log still says 36000. Is there a
separate settings at ekiga.net? Is there a way
for me to set it?
I set it to 3600 in gconf
(sip:registrar_registration_timeout as well as in
accounts_list) but it seems that both settings are
ignored? The log still says 36000. Is there a
separate settings at ekiga.net? Is there a way
for me to set it?
Sorry for my monologue... It turned out that the
Le mercredi 24 décembre 2008 à 22:19 +0100, Palo S. a écrit :
http://lists.openser.org/pipermail/users/2008-March/016618.html
This reply is internally generated by the blacklists core - the
destination IP address was blacklisted (maybe due a 50x or timeout
to previous response).
Offline is sent back when the user is not in the database anymore.
Perhaps it did not refresh the registration in time ? That is something
you should look in his log : is there a REGISTER request to renew the
registration or not.
I do not have a log from the other side, maybe I will
succeed
I don\\\'t know whether this is related to the issue we
have in this thread...
Now I know - it is related. It seems to be a pattern:
After some time (seems to be around 1-2 hours from Ekiga
start) there is no communication anymore between the
client and the server. The client still
Le mercredi 24 décembre 2008 à 01:53 +0100, Palo S. a écrit :
Recently, it happened to me several times that I could not
initialize a call although I knew for sure that the other
side was online. Also, I got similar complaints from others
not able to reach me by Ekiga but when they used eg
http://lists.openser.org/pipermail/users/2008-March/016618.html
This reply is internally generated by the blacklists core - the
destination IP address was blacklisted (maybe due a 50x or timeout
to previous response). This is a self-protection mechanism to prevent
sending requests to
28 matches
Mail list logo
