Re: [Ekiga-list] ANNOUNCE - Ekiga 3.3.0 [UNSTABLE] available

2010-12-21 Thread Palo S.

Great, congratulations!
I tried to compile it and I managed to compile everything
(ptlib, opal, ekiga - well, h264 did not compile so I
disabled it) but it breaks at linking, with undefined 
XInitThreads. What version of Xorg/Xlib is needed?
(addding /usr/lib64/libX11.so.6 to the linker
command did not work either)

/usr/bin/ld: main_window.o: undefined reference to symbol 'XInitThreads'
/usr/bin/ld: note: 'XInitThreads' is defined in DSO /usr/lib64/libX11.so.6 so 
try adding it to the linker command line
/usr/lib64/libX11.so.6: could not read symbols: Invalid operation

_

http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-29 Thread Palo S.

 I restarted it.

Still no registration here. Either it is down again or
my client is playing with me...
_

http://fotky.sme.sk - Ukazte svoje najlepsie fotky svetu
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-29 Thread Palo S.

 Your client is playing with you...

Thanks for information! I am going to look at it more 
closely then...
_

Sprievodca hernym svetom - http://hry.sme.sk/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-29 Thread Palo S.

 Could it be the ISP the one who is banning the address?

Nope, it seems to be the client. It keeps on getting
606 Not Acceptable, however, I can register from a different 
computer from the same LAN. Strange but at least I know
the problem is on my side this time.
_

Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] server down?

2010-11-28 Thread Palo S.

Repeatedly cannot register from different locations
and for different accounts. Looks like the server is
down again.
_

http://kultura.sme.sk/ - Informacny server o kulture a soubiznise
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-28 Thread Palo S.


 Repeatedly cannot register from different locations
 and for different accounts. Looks like the server is
 down again.

Still no registration. Can somebody please confirm the 
problem and/or (preferably) restart the server? 
_

Najpopularnejsi blog na Slovensku - http://blog.sme.sk/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-28 Thread Palo S.

Andrew  Rob: The same behaviour with my clients. They reported
they were registered but no calls could be made. After the
deregistration, all registration attemps fail with Could
not register (Globally not acceptable). It lasts for the last
5 hours approximately. 

So it seems the server is really having issues but I am afraid
we have to wait till somebody with access to it notices and
fixes the problem... 

This actually happens quite frequently and it usually takes 
hours or even days sometimes to get fixed. I think it might 
be an idea to arrange a better means of communication to get 
the message about the server issues to its administrators 
delivered promptly because apparently they are not reading 
these threads all the time. Something like report a probable
server problem button on a webpage or in the client with 
message delivered to a frequently read addresses the admins 
set. Or is there something like already I just don't know 
about?



_

http://diplomovka.sme.sk - Odmenujeme vale diplomove prace.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down?

2010-11-28 Thread Palo S.

 I've noticed that kind of thing in the past.  It's what made me go and
 get a free account at iptel.org.  Their service seems to be much more
 reliable, and it works fine with the ekiga software.

That means no video though, right? 
_

Ponuky prace, brigady a personalne poradenstvo - http://praca.sme.sk
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] client not receiving calls: EndedByTemporaryFailure

2010-11-15 Thread Palo S.

Hi Eugen,

thanks for the answer! I suspect it might actually be
a combination of more reasons causing the issue:
I experienced this also in 3.2.6 but the behaviour was 
bit different - it appeared less frequently and as far 
as I can tell, not before the first call (which suggests 
your third reason). 
With 3.2.7 it is more frequent and if I remember correctly, 
even the log that I uploaded shows that it happens also
before any call is made - so also first or second reason
seems to get involved in 3.2.7. The 3.2.7 bugfix list 
mentions 'Fix many connection issues (nat ports)' which
I suspect might have caused this regression.
_

http://kultura.sme.sk/ - Informacny server o kulture a soubiznise
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Bug in ekiga - busy signal after a day or two of being idle

2010-11-14 Thread Palo S.

 To whom it might interest. 
 
 When my computer has been powered on for maybe one or two days, anyone who 
 calls me from an ordinary phone to  ekiga gets a busy signal. I works just 
 fine when Ekiga was just started. 

Welcome in the club. I have reported similar issue a week 
ago to this list, although I get 'not available' instead
of your 'busy' and it does not take days but often just 
tens of minutes. Restart of Ekiga fixes the problem for 
some time exactly as in your case.

 
 I have two accounts set up in ekiga. One Ekiga.net account and one Phonzo.com 
 account. 
 
 It is the phonzo.com account that stops working. I don't know if the same is 
 true for the ekiga.net account. 
 
 Is this a known bug in Ekiga? 

I guess this and many similar reports are NAT related and
nobody really knows how to deal with them properly due to
the plethora of slightly different NAT implementations.

I ended up writing an ugly hack - a script catching -d 2
output of ekiga and restarting it every ten minutes unless
-d 2 suggests ekiga is in call... Not very nice indeed but 
at least Ekiga is usable with this hack again...
_

Najvyhodnejsie povinne poistenie aut - http://poistenie.sme.sk
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] client not receiving calls: EndedByTemporaryFailure

2010-11-08 Thread Palo S.

Nobody has any idea what could be going on? Even the 
logs from both sides are not useful? Should I file 
a bug report or is this a known problem?

_

http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] client not receiving calls: EndedByTemporaryFailure

2010-11-08 Thread Palo S.
@Pál: I think it is a different issue: you receive
405 Method Not Allowed and EndedByQ931Cause, I get
480 Offline and EndedByTemporaryFailure... although,
it is possible that both are NAT issues and somehow
related...

@Eugen: Thanks!

P.


- Originálna správa -
Odosielateľ: Csányi Pál csanyi...@gmail.com
Komu: Ekiga mailing list ekiga-list@gnome.org
Dátum: pondelok, november 8, 2010 04:27:26
Predmet: Re: [Ekiga-list] client not receiving calls: EndedByTemporaryFailure

Hi Palo,

2010/11/8 Palo S. pa...@post.sk:

 Nobody has any idea what could be going on? Even the
 logs from both sides are not useful? Should I file
 a bug report or is this a known problem?


Mybe this is the same problem that I have:
http://mail.gnome.org/archives/ekiga-list/2010-November/msg00027.html

-- 
Regards, Paul Chany
http://csanyi-pal.info
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
_

Pridajte si zivotopis na http://praca.sme.sk, aby vas zamestnavatelia nasli.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] client not receiving calls: EndedByTemporaryFailure

2010-11-06 Thread Palo S.
For a long time, I am having a problem of Ekiga client not receiving 
calls sometimes, with user not available explanation on the calling
side. With recent upgrade to 3.2.7, the situation seems to be even 
worse than before (with 3.2.6) - more calls are actually not received 
than received... After restart of the client, it usually receives calls 
again for some time at least.

I have caught -d4 log from both sides: 
ftp://quacka.no-ip.org/pub/ekiga_temporary_failure.tgz
The log on the caller side (at 18:42:11 and repeated attempt at 18:42:22) 
says the call is ended because of EndedByTemporaryFailure reason. 
On the called side, I cannot find anything about the attempted call.

Is this a known problem? 
_

Chcete zmenit svoje zamestnanie? Viac na http://praca.sme.sk
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] nikolai: Wanted to know if it was okay to use ekiga 3.2.7 over my current 3.2.6

2010-08-14 Thread Palo S.
 Hi, I am running ubuntu 10.04 and wanted to know if I could upgrade my
 ekiga 3.2.6 to 3.2.7 as some bugs occur with my current version of
 3.2.6, such as Ekiga can't receive calls after some time and some
 incoming calls won't ring but you can answer.  Since 3.2.7 is latest
 version, I figured it probably got rid of those problems so I wanted to
 know if I should update to 3.2.7?

I can second what Wiliam said: it is not worth upgrading
as these bugs are not fixed in 3.2.7 - a workaround that
seems to work for me is to restart Ekiga after every call
(sometimes killing is necessary if Ekiga stops responding).
Furthermore, 3.2.7 introduced a new bug of Ekiga not being 
able to receive calls in situations when 3.2.6 was able; 
probably something NAT related - the problem disappeared 
after downgrading to 3.2.6. 
(Unfortunately I was not able to reproduce the problem 
when calling between my own computers, so no logs/bugreport)

P.
_

Sprievodca hernym svetom - http://hry.sme.sk/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] nikolai: Wanted to know if it was okay to use ekiga 3.2.7 over my current 3.2.6

2010-08-14 Thread Palo S.

 So there is no way to work around the bug of ekiga stop working after
 some time, the only solution is to restart every time.

With 3.2.6, I get the problems of Ekiga randomly not receiving 
calls, not quiting normally, not ringing etc only after the 
first call - at least I never noticed them before the first 
call. Thus restarting after every call is a workaround for me. 
With 3.2.7, Ekiga did not receive calls also before the
first call. But perhaps this behaviour is only specific
for my setup... 
As soon as I catch a log of the 3.2.7 regression, I'll send 
them, however at the moment I use 3.2.6...

P.
_

http://sport.sme.sk - Najkomplexnejsie informacie zo sportu
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] nikolai: Wanted to know if it was okay to use ekiga 3.2.7 over my current 3.2.6

2010-08-14 Thread Palo S.

 There was a bug when ekiga won't receive calls when ih has previously 
 received a call while in communication, but it was fixed in 3.2.7 cf. 
 http://git.gnome.org/browse/ekiga/commit/?h=gnome-2-26id=3b636f02e. 
 Maybe it has not been fixed completely...

Who knows, this may be related, however, there is certainly more
to the story. For instance, it happened quite a few times that 
I received a call, from whatever reason cancelled it after a few 
seconds (very small chance of another incoming call in the same 
time) and yet the problems appeared. 
_

Najpopularnejsi blog na Slovensku - http://blog.sme.sk/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Could not register (Globally not acceptable)

2009-12-28 Thread Palo S .

Exactly the same issue here with 3.2.6 and Fedora 12. 
Looks like a server problem.

- Originálna Správa -
Od: Fedor Von Bock  
Komu:  
Poslaná: 28.12.2009 04:04 
Predmet: [Ekiga-list] Could not register (Globally not acceptable)

 Hi,
 
 on ubuntu karmic i\'m using ekiga 3.2.5...When i try ti register the
 ekiga.net account i get the above message Could not register (Globally
 not acceptable).
 
 Other account, (diamondcard) seems to register fine so I don\'t think
 it\'s a firewall or NAT router problem
 
 
 
 Thanks,
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Could not register (Globally not acceptable)

2009-12-28 Thread Palo S .

It is an Ekiga STUN server issue. The registration works
when I change the STUN server.


- Originálna Správa -
Od: Palo S.  
Komu: ,  
Poslaná: 28.12.2009 16:34 
Predmet: Re: [Ekiga-list] Could not register (Globally not acceptable)

 
 Exactly the same issue here with 3.2.6 and Fedora 12.
  Looks like a server problem.
 
 - Originálna Správa -
 Od: Fedor Von Bock
   Komu:
   Poslaná: 28.12.2009 04:04
  Predmet: [Ekiga-list] Could not register (Globally not acceptable)
 
  Hi,
 
   on ubuntu karmic i\\\'m using ekiga 3.2.5...When i try ti register the
  ekiga.net account i get the above message Could not register (Globally
  not acceptable).
 
   Other account, (diamondcard) seems to register fine so I don\\\'t think
  it\\\'s a firewall or NAT router problem
 
  
  
   Thanks,
 
   ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 
 
 
  __
 Najpopulárnejší blog na Slovensku - http://blog.sme.sk/
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Could not register (Globally not acceptable)

2009-12-28 Thread Palo S .

It is done via gconf editor (a bit unfortunate that
it is not posible from the client directly), I used
gconf-editor GUI to do that. It is the
apps-ekiga-general-nat-stun_serevr option.



- Originálna Správa -
Od: Fedor Von Bock  
Komu:  
Poslaná: 28.12.2009 17:39 
Predmet: Re: [Ekiga-list] Could not register (Globally not acceptable)

 how do you change it?
 
 Palo S. wrote:
  It is an Ekiga STUN server issue. The registration works
  when I change the STUN server.
 
 
  - Originálna Správa -
  Od: Palo S.  
  Komu: ,  
  Poslaná: 28.12.2009 16:34 
  Predmet: Re: [Ekiga-list] Could not register (Globally not acceptable)
 

  Exactly the same issue here with 3.2.6 and Fedora 12.
   Looks like a server problem.
 
  - Originálna Správa -
  Od: Fedor Von Bock
Komu:
Poslaná: 28.12.2009 04:04
   Predmet: [Ekiga-list] Could not register (Globally not acceptable)
 
  
  Hi,
 

on ubuntu karmic i\\\'m using ekiga 3.2.5...When i try ti register 
  the
  
  ekiga.net account i get the above message Could not register (Globally
  not acceptable).
 

Other account, (diamondcard) seems to register fine so I don\\\'t 
  think
  
  it\\\'s a firewall or NAT router problem
 

   
   
Thanks,
  
___
  
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 

   __
  Najpopulárnejší blog na Slovensku - http://blog.sme.sk/
 
 
  ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 
  
 
 
  __
  http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise
 
 

 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://zabava.sme.sk/ - Stránka čo usmeje ti tvár


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Cannot register to ekiga.net

2009-10-24 Thread Palo S .

Yes, STUN server is down. You can use another STUN server 
to get Ekiga working, at least for the audio part. 

P.




- Originálna Správa -
Od: Kevin Wilson  
Komu: Ekiga mailing list  
Poslaná: 24.10.2009 10:19 
Predmet: Re: [Ekiga-list] Cannot register to ekiga.net

 Andre,
   Thanks a lot for you response!
  This is due to stun.ekiga.net being down
 
 Are you sure this is the reason ?
 
 I have now ping to stun.ekiga.net, and still get this error (\Could
 not register - (Globally not acceptable) \) when I try to register
 with ekiga.
 
 Of course it could be that the stun server is temporarily not running
 on this machine, and I wonder whether indeed this is the case.
 
  Can I say, without any chance of being wrong, that getting this error
 (\Could not register - (Globally not acceptable) \))
 indicates about that the stun server of stun.ekiga.net is down?
 
 
 Regards,
 Kevin
 
 On Fri, Oct 23, 2009 at 7:01 PM, Andre Robatino  wrote:
  This is due to stun.ekiga.net being down - see
 
  http://mail.gnome.org/archives/ekiga-list/2009-October/msg00164.html
 
  Since Ekiga requires registration to a STUN server, it might be a good
  idea if there was a STUN server running on the same machine as the
  registration server, for reliability.
 
 
  ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Svetova kniznica SME - literarne klenoty 20. storocia - http://knihy.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga failing to register

2009-07-19 Thread Palo S .

ekiga.net is down this weekend from some reason.
See the previous threads about the same topic...



- Originálna Správa -
Od: David Fox  
Komu: Ekiga mailing list  
Poslaná: 19.07.2009 21:42 
Predmet: Re: [Ekiga-list] ekiga failing to register

 On Sun, Jul 19, 2009 at 11:59 AM, Paul Barron wrote:
  Is anyone elses ekiga failing to register today?
 
 Not working for me either.
 
 
 
 -- 
 thanks for letting me change the magnetic patterns on your hard disk.
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://chat.post.sk - zachatujte si s priatelmi na IRC.POST.SK


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down again

2009-07-18 Thread Palo S .

Down again...

- Originálna Správa -
Od: Damien Sandras  
Komu: Ekiga mailing list  
Poslaná: 12.07.2009 14:47 
Predmet: Re: [Ekiga-list] server down again

 Le dimanche 12 juillet 2009 Ă  13:58 +0200, Michael Rickmann a ĂŠcrit :
  Damien Sandras schrieb:
   Le samedi 11 juillet 2009 Ă  18:41 -0400, Andre Robatino a ĂŠcrit :
   Down again.
   
   Restarted.
   
   As I said, somebody is having fun during the night and crashes it.
  I am not quite shure that it is not me. I am trying to find a bug of 
  Win32 Ekiga. It seems opal/ptlib related and is unfortunately also in 
  the versions needed for Ekiga 3.2.5. Instead of opening the audio device 
  when a call has been established to 5...@ekiga.net, windows are piling up 
  and render XP or Win7 rather unusable. Surprisingly this does not happen 
  when connecting to a local Ekiga 2.0.10 by direct IP. So I have to kill 
  Ekiga before Windows gets stuck. Please keep starting ekiga.net so that 
  I can continue bisecting ptlib/opal.
 
 I have put a script. It should not go down anymore.
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://www.inzeraty.sk/ - Bezplatná inzercia v najobľúbenejších kategóriách


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] server down again

2009-07-18 Thread Palo S .

Still down the whole day. Can somebody please restart it?



- Originálna Správa -
Od: Palo S.  
Komu:  
Poslaná: 18.07.2009 11:57 
Predmet: Re: [Ekiga-list] server down again

 
 Down again...
 
 - Originálna Správa -
 Od: Damien Sandras
   Komu: Ekiga mailing list
   Poslaná: 12.07.2009 14:47
  Predmet: Re: [Ekiga-list] server down again
 
  Le dimanche 12 juillet 2009 Ă  13:58 +0200, Michael Rickmann a ĂŠcrit :
   Damien Sandras schrieb:
Le samedi 11 juillet 2009 Ă  18:41 -0400, Andre Robatino a ĂŠcrit :
Down again.
   
 Restarted.
   
 As I said, somebody is having fun during the night and crashes it.
   I am not quite shure that it is not me. I am trying to find a bug of
Win32 Ekiga. It seems opal/ptlib related and is unfortunately also in
the versions needed for Ekiga 3.2.5. Instead of opening the audio device
when a call has been established to 5...@ekiga.net, windows are piling up
and render XP or Win7 rather unusable. Surprisingly this does not happen
when connecting to a local Ekiga 2.0.10 by direct IP. So I have to kill
Ekiga before Windows gets stuck. Please keep starting ekiga.net so that
I can continue bisecting ptlib/opal.
 
   I have put a script. It should not go down anymore.
  --
_ Damien Sandras
  (o-
//Ekiga Softphone : http://www.ekiga.org/
  v_/_   Be IP   : http://www.beip.be/
 FOSDEM  : http://www.fosdem.org/
 SIP Phone   : sip:dsand...@ekiga.net
 
 
   ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 
 
 __
 http://www.inzeraty.sk/ - Bezplatná inzercia v najobžúbenejších kategóriách
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://www.pnp.sk -  pridajte svoje fotky na PaciNepaci


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Ekiga contact presence

2009-07-11 Thread Palo S .

  My girlfriend turns off ekiga, but I still see her online, when I come
  back I try calling, after restarting ekiga this status is updated.

I can confirm the problem and it behaves like this on 4
different computers in 4 different networks (everywhere
where I tried it) : If the other side connects, the status 
updates quickly, if the other side quits, the status 
_never_ gets updated. If I leave the client up for several
days then I end up with all my contacts permanently green.
I had this behaviour from the very first Ekiga 3.0 that
I installed.



  If I remember correctly, when a person quits ekiga, there is no update 
  sent on the server.  However, the server (or the client) periodically 
  (15 min I think) sends info to remote party about the presence.  So, 
  when a person quits ekiga, it will take at most 15 min to update his 
  presence.

Interesting. I would assume that this could occasionaly 
cause the opposite problem (ie not showing online status
when contact is online). But I cannot see how it can actually 
happen that the client never gets the offline status of
the contact if the \default\ behaviour (ie when no message 
is delivered to the server within 15 minutes) is offline 
status and if the communication between the server and client 
is clearly there (eg new contacts getting online become
green). I suspect a bug.



 What about sending a message to the server \I\'m disconnecting\... and 
 *not* wait for any answer?

The same thing came to my mind after reading the previous
messages in this thread. I imagine that it could be quick
and safe to implement.

Palo



__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ANNOUNCE - Ekiga 3.2.4 [STABLE] available

2009-05-20 Thread Palo S .

Thanks for all these bugfix releases! I know it 
must have been a pain. But the important thing
is that it should be ok now. I will test soon
as well (and perhaps only report any problems 
later - I think the developers deserve some
rest now :)

P.


- Originálna Správa -
Od: Damien Sandras  
Komu: , Ekiga mailing list , Ekiga mailing list  
Poslaná: 20.05.2009 10:55 
Predmet: [Ekiga-list] ANNOUNCE - Ekiga 3.2.4 [STABLE] available

 This is the fourth stable release of the 3.2 release series of Ekiga.
 
 
 * What is it ?
 ==
 
 Ekiga is a free Voice over IP softphone allowing you to do free audio 
 and video calls over the Internet.
 
 Ekiga is the first Open Source application to support both H.323 and
 SIP, as well as audio and video.  Ekiga was formerly known as
 GnomeMeeting.
 
 More information can be found at http://www.ekiga.org
 
 
 * Where to get it ?
 ===
 
 Ekiga is available at:
 ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.2 (take 3.2.2)
 
 Required librairies can be found at:
 ftp://ftp.gnome.org/pub/gnome/sources/opal/3.6/ (take 3.6.2)
 ftp://ftp.gnome.org/pub/gnome/sources/ptlib/2.6/ (take 2.6.2)
 
 
 * What\'s changed ?
 ==
 
 It contains a fix for invalid OPAL and PTLIB recommended versions.
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://www.tahaj.sk - Najnavstevovanejsia stranka slovenskeho downloadu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] ekiga.net problems again?

2009-04-26 Thread Palo S .

I cannot register to ekiga.net from two computers in
different countries for around 30 minutes now. Is 
there a problem with ekiga.net again?

P.


__
http://auto.sme.sk - Všetko o autách (novinky, testy, autosalón, autoškola, 
porovnaj si auto)

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Ekiga white page are down.

2009-04-03 Thread Palo S .

If this means that the \unknown callers\ (which
often bother several times a day) cannot find
my SIP address anymore, then it is actually 
a good thing... I would actually vote for shutting
the white page down until it is not possible for 
the user to remove his address from there!

Palo


- Originálna Správa -
Od: yannick  
Komu: Ekiga development mailing list , Ekiga mailing list  
Poslaná: 03.04.2009 12:58 
Predmet: [Ekiga-list] Ekiga white page are down.

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hello,
 
 Since at last Fri, 03 Apr 09 11:22:00 +0200, the Ekiga white pages are down.
 
 We are trying our best to fix this issue as soon as possible.
 
 Sorry for that.
 
 Best regards,
 Yannick
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iEYEARECAAYFAknV67wACgkQaP9jcuuuScBfegCdFul5NqaGyKrtVL4zXuJy6541
 lhkAoJh5/vq9Ch3PWbbqXOjRzxX8hWvk
 =pC96
 -END PGP SIGNATURE-
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga on Slackware 12.2 not workingusefully... any suggestions?

2009-02-26 Thread Palo S .
 
 Now ekiga sees my camera.  However
 (1) if it receives a call from an ekiga 3.0.1 or 3.1.0 system it seg
 faults and dies.
 It also makes the complaints
 
 ** (ekiga:22591): CRITICAL **: gm_conf_get_string: assertion `key 
 /apps/ekiga/general/user_interface/main_window/size has no corresponding 
 entry! \' failed
 
 ** (ekiga:22591): CRITICAL **: entry_get_bool: assertion `gmconf key 
 /apps/ekiga/general/nat/disable_stun is of type GM_CONF_BOOL\' failed
 

This really looks like gconf/gnome related issue.
However I cannot say whether this cause the problem.

 
 I have to assume that there is some weird thing going on in my system
 that none/few of you see.  Is there anyone here (besides me) else
 using it with
   --disable-gnome --disable-gconf
 
 Thanks for any suggestions anyone can provide.

Maybe you can try to compile with gnome and gconf 
support? In order to find out whether it is the 
cause of the  problem or something else is on 
blame...

P.



__
http://www.pnp.sk -  pridajte svoje fotky na PaciNepaci


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] presence support has never worked

2009-01-30 Thread Palo S .

 the case, then you probably think you are running 3.0.2 with OPAL 3.4.4,
 but it is not the case.

This is happens surprisingly often. Wouldnt it be 
useful if the ptlib version was outputted in the 
-d4 log?

BTW \up to 1 hour\ for online-offline means usually 
many hours for me... I can see people online that I
know for sure were last online a day before. Or do I
face another problem? offline-online seems to work
much better for me also.

Palo



__
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] presence support has never worked

2009-01-30 Thread Palo S .

 This is happens surprisingly often. Wouldnt it be 
 useful if the ptlib version was outputted in the 
 -d4 log?

Ignore my comment. As Michael pointed out it is in
the log already and it is 3.4.4 indeed.



__
http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga 3.0 and ssh -X

2009-01-19 Thread Palo S .


 Le dimanche 18 janvier 2009 Ă  20:08 -0800, lifu a ĂŠcrit :
  I\'m running ekiga 3.0 on Ubuntu 8.10 MID device. There is some
  problems within our graphic driver, so I will have to run it remotely
  using ssh -X to get it work around. Ekiga won\'t start, it errors in
  
  libnotify-Message: Unable to get session bus: Failed to connect to
  socket /tmp/dbus-SqkURgxppA: Connection refused
  
  On the other side, I could start skype via ssh -X without a problem.
  Why is that? What\'s the difference? Is there anyway to run ekiga just
  using commands? BTW, ekiga works just fine if I do it on X-window. The
  error is only seen in remote X. The verbose message is shown below
 
 Compile it without libnotify support... I suppose the notification
 daemon can not communicate with ekiga, leading to the problem.

ssh -X-ing ekiga works very well for me (and with
several machines) with libnotify compiled in, I
wold guess it may be distribution specific problem
(depending how the distribution sets dbus, libnotify)
Disabling libnotify is certainly something to try.

Palo



__
Svetova kniznica SME - literarne klenoty 20. storocia - http://knihy.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] SMS with Ekiga?

2009-01-11 Thread Palo S .

 Sorry, I never read anything in freecall about sip. Maybe they use it in 
 the background? Sorry, I dont know, thats too high for me yet.
 

I am afraid that you may need to use their program
to use their SMS services. Or do you know of any other 
program other than theirs (also under Windows) that 
enables that? I would be surprised.

However you can still send SMS through their website
or since you are using Ekiga for pc-phone calls,
also through Ekiga via Diamond.

P.



__
http://zabava.sme.sk/ - Stránka čo usmeje ti tvár


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] SMS with Ekiga?

2009-01-11 Thread Palo S .

- Originálna Správa -
Od: Judith Meili  
Komu: Ekiga mailing list  
Poslaná: 11.01.2009 19:20 
Predmet: Re: [Ekiga-list] SMS with Ekiga?

 
 Its not possible to use the freecall program with Linux. I have to use 
 Ekiga to use freecall with Linux.

Nope, I know, but I am afraid this complaint should
be addressed to freecall... you know, there are
services better supported under Windows and simply
Freecall is one of them. Your choice is a) use
Freecall and Windows, b) use Frecall and Linux with
limited support for eg SMS sending, c) use Linux
with a more Linux-friendly service eg Diamond in
Ekiga (just an example - I don\'t use it personally
so cannot say how that works but presumably ok)

Palo


 
 Palo S. schrieb:
  Sorry, I never read anything in freecall about sip. Maybe they use it in 
  the background? Sorry, I dont know, thats too high for me yet.
 
  
 
  I am afraid that you may need to use their program
  to use their SMS services. Or do you know of any other 
  program other than theirs (also under Windows) that 
  enables that? I would be surprised.
 
  However you can still send SMS through their website
  or since you are using Ekiga for pc-phone calls,
  also through Ekiga via Diamond.
 
  P.
 
 
 
  __
  http://zabava.sme.sk/ - Stránka čo usmeje ti tvár
 
 
  ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 

 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] H264: PP: Error when trying to create DL named pipe

2009-01-11 Thread Palo S .



- Originálna Správa -
Od: Palo S.  
Komu:  
Poslaná: 11.01.2009 20:42 
Predmet: [Ekiga-list] H264: PP: Error when trying to create DL named pipe

 
 I noticed that the following sometimes happens right
 after the start of EKiga:
 
 dyna.cxx(111)   H264DYNASuccessfully loaded 
 \\\'libavcodec.so.51\\\'
 dyna.cxx(331)   H264DYNASuccessfully loaded libavcodec 
 library and verified functions
 h264pipe_unix.cxx(192)  H264IPC PP: Error when trying to create DL 
 named pipe
h264-x264.cxx(838)   H264Codec   Disabled
 
 After that H264 is disabled and does not appear among
 the audio codecs in preferences

it is even worse: it does not even appear among video
codecs ;)

P.

 it reappears again
  after Ekiga restart however \\\unticked\\\ and as the last
 codec. If I tick it and move higher, I can do H264
 videos without problem and it usually works fine
 for several Ekiga restarts until suddenly the error
  appears again. I do not see any pattern unfortunately
 for when the error occurs and when not.
 
 Does anybody have any idea what could be the problem
 or what could be done?
 
 P.
 
 
 
 __
 http://sport.sme.sk - Najkomplexnejšie informácie zo športu
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje 
myšlienky, zážitky a nové informácie - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Registration Failed: Timeout

2009-01-10 Thread Palo S .
 
 jaysus!
 i should have don\'t that as the first thing!!!
 it works! so the old account is busted...
 thanks!
 

The simplest solutions are often the best :)
I am glad it helped,

Palo



__
http://zabava.sme.sk/ - Stránka čo usmeje ti tvár


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): Re^6: Audio-Problems

2009-01-10 Thread Palo S .


 I have a similar problem.  I have an Audigy sound card using ca0106, and a 
 USB 
 headset using snd-usb-audio.  I have adapted your modprobe.conf, but how do 
 you switch between them?  For a while they were loaded automatically 
 according to the application I opened, but no longer.
 
The index keyword in modprobe only defines the order
of the devices, ie you can be sure that eg device 0 is 
always ca0106 and device 1 is snd-usb-audio. You still
need to say each application which of your devices it
should use, every application dealing with sound should
have settings enabling to specify the device (eg in
Ekiga under Preferences-Audio Devices). index in modprobe
then assures that the devices will be assigned always
the same and you won\'t need to change the application
settings after reboots.

P.



__
http://www.tahaj.sk - Najnavstevovanejsia stranka slovenskeho downloadu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Yet an other post on Pulseaudio

2009-01-10 Thread Palo S .


 First I need to learn how to disable pulseaudio, then I will have a better 
 clue where the issue is.
 

yum remove pulseaudio

P.



__
http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] [Fwd: Audio-Problems]

2009-01-04 Thread Palo S .


- Originálna Správa -
Od: Judith Meili  
Komu: Ekiga mailing list  
Poslaná: 04.01.2009 10:07 
Predmet: [Ekiga-list] [Fwd: Audio-Problems]

 
 Dear all
 
 What do I need to do? After closing skype, Ekiga is still not working. 
 Always the same message below.
 

It should. Which version of Ekiga, Skype, which 
operating system and which soundcard do you use? 
Does it also not work if you restart Ekiga after 
closing Skype? It looks like Skype blocks the
soundcard which could be caused by an older 
version of Skype for instance...

 Br
 jm
 
  Original-Nachricht 
 Betreff:  Audio-Problems
 Datum:Tue, 30 Dec 2008 08:29:19 +0100
 Von:  Judith Meili 
 An:   Ekiga mailing list 
 
 
 
 Hello
 
 Why do I get this message?
 
 \Audiokanal zum Audioempfang konnte nicht geöffnet werden
 
 Beim Versuch, Audio für den Audio-Empfang über die Soundkarte 
 auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die 
 Soundkarte nicht anderweitig benutzt wird und dass der Treiber 
 Voll-Duplex unterstützt.
 Der Audioempfang wurde deaktiviert.\
 
 Br
 jm
 
 
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Problem with SIP registration in Ekiga

2009-01-04 Thread Palo S .

If you have access to another STUN server then you can
try that. It solved the problem of not being able to
register several times for me (I don\'t know why)

- Originálna Správa -
Od: Brian  
Komu: \Ekiga mailing list\  
Poslaná: 04.01.2009 13:16 
Predmet: Re: [Ekiga-list] Problem with SIP registration in Ekiga

 On Sun, 04 Jan 2009 21:41:18 +1000, Uditha M de Soysa  
  wrote:
 
  Hi,
 
  I\'m using ekiga 2.0.12 in Ubuntu 8.10. I have problem with connecting to
  my SIP account. Sometimes it connects. sometimes it doesn\'t. I\'m using  
  NAT
  traverdsal \'STUN\', and STUN server \'stun.ekiga.net\'.
 
  ANd im using a HSPA connection for internet
 
  I have enable the ip_port_forwarding to \'1\' too.
 
  Pls, help me on this situation.
 
 
 I have just upgraded to 3.0.1. I can recommend this path if you can.
 In the process of setting up to register with my new provider I did a test  
 to ekiga.net,which worked.
 When I tried to register with my provider it failed.
 So I removed the ekiga.net account and it still failed.
 I then ran wireshark(also recommended to see what is going on) and found  
 that my register process was still trying to use the stun server.
 To remove this you have to use gconf-editor. See previous posts.
 Not sure why it was failing when it used the stun server, but it looked  
 like it might have been a timing thing.
 
 Now my router has the uPnP facility, which enables applications to find  
 there way through the NAT(if started from inside), also my provider does  
 not require a stun server.
 Not sure if this was required, in any event the next time I tried to  
 register it worked and has been working ever since.
 So what I am suggesting is removing the stun server may be worthwhile.
 
 I also note that  you say your connection works \'sometimes\'.
 I guess there could be many circumstances for this, but his is one and is  
 easy to check.
 
 I shut ekiga down once and it would not reregister.
 On checking my router I found that it was still holding the listening port  
 up, in my case that was port 5065 but it is normally 5060.
 I just waited for the timeout in the router and ekiga reregistered  
 straight away.
 So you could check how long your router holds a port up for after it has  
 been disconnected.
 
 As always YMMV with any of the above, because I cannot see what is  
 actually going on.
 However, I say again it is worth getting to know wireshark.
 
 Brian
 
 
 
 -- 
 Using Opera\'s revolutionary e-mail client: http://www.opera.com/mail/
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://www.pnp.sk -  pridajte svoje fotky na PaciNepaci


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): Re^6: Audio-Problems

2009-01-03 Thread Palo S .

You can specify the order of sound drivers loading
in your modprobe file. I have three sound devices
in my main home computer (every device used with
different program) and the specification of order
is very reliable. These are the lines I use 
(I think they are self-explanatory, if not then you 
can certainly find more info with google):

alias snd-card-0 snd-emu10k1
options snd-emu10k1 index=0
remove snd-emu10k1 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; }; 
/sbin/modprobe -r --ignore-remove snd-emu10k1
alias snd-card-1 snd-intel8x0
remove snd-ca0106 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; }; 
/sbin/modprobe -r --ignore-remove snd-ca0106
options snd-intel8x0 index=1
remove snd-intel8x0 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; }; 
/sbin/modprobe -r --ignore-remove snd-intel8x0
alias snd-card-2 snd-usb-audio
options snd-usb-audio index=2

Hope this helps,

Palo


- Originálna Správa -
Od: PETER EASTHOPE  
Komu:  
Poslaná: 03.01.2009 18:02 
Predmet: [Ekiga-list] Re (2):  Re^6:  Audio-Problems

 Folk,
 
   ... versions of Ekiga and Skype ... problem ... 
 
 The worst difficulties for me are with audio 
 devices rather than with applications which use 
 them.  The USB-audio adapter always initializes 
 but the on-board Intel audio sometimes fails.  
 I\'ll guess that this involves timing of startup 
 processes.
 
 When the Intel audio is absent, the Skype icon 
 appears as usual.  Hours or days later, after 
 a correspondent complains that I didn\'t answer 
 a call, ringing is found to be redirected 
 from the speakers to the headset.  Skype never 
 indicates this of course.
 
 Appears that when Ekiga fails to find a device, 
 the toolbar icon is not displayed.  A rational 
 behaviour; thanks to Ekiga.
 
 I\'m phasing out Skype DID in favour of Ekiga 
 DID and hoping the flaws in Linux device 
 initialization are fixed, sooner rather than 
 later. 
 
 Regards,... Peter E.
 
 
 -- 
 http://members.shaw.ca/peasthope/
 http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://chat.post.sk - zachatujte si s priatelmi na IRC.POST.SK


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): Re (2): Re (2): Audio-Problems

2009-01-02 Thread Palo S .

Hi Peter,

unfortunately I can\'t remember the versions of Ekiga
and Skype that caused this problem for me. It could
have been even beta versions of Ekiga/Skype that I
used for some time too. I can only say that my current 
setup (Ekiga 3.0.1 from source, skype-2.0.0.72-fc5
rpm package on Fedora 8) does not suffer by this.

Palo



- Originálna Správa -
Od: PETER EASTHOPE  
Komu:  
Poslaná: 02.01.2009 18:01 
Predmet: [Ekiga-list] Re (2):  Re (2):  Re (2):  Audio-Problems

 Palo,
 
  ... while Skype was idly running (not in call), 
 Ekiga was not able to produce any sound when I 
 was trying to make a call with it. 
 
 I\'ve tried 4 calls with Ekiga while the 
 Skype daemon was in the background.  Three of 
 the calls were fine.  Yesterday afternoon in 
 one of the trials the system froze so solid 
 it needed to be power cycled; there is no 
 good evidence that Skype or Ekiga is at fault.
 
 This is Debian Lenny with Ekiga 2.0.12 and 
 Skype 2.0.0.72.  
 
 A machine at work has Ekiga 3; this one 
 will be upgraded soon.
 
 Regards,   ... Peter E.
 
 -- 
 http://members.shaw.ca/peasthope/
 http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): Re (2): Audio-Problems

2009-01-01 Thread Palo S .

- Originálna Správa -
Od: PETER EASTHOPE  
Komu:  
Poslaná: 31.12.2008 22:24 
Predmet: [Ekiga-list] Re (2):  Re (2):  Audio-Problems

 Palo,
 
 ps Ekiga audio did not work when Skype was running. 
 
 Do you mean that you want to hear the ring 
 from an incoming call to Ekiga while a Skype 
 conversation is in progress?  Or do you mean 
 that the Skype daemon is merely idle in the 
 background when Ekiga rings?  

nope, I meant something else: while Skype was idly 
running (not in call), Ekiga was not able to produce 
any sound when I was trying to make a call with it. 
I understand this is the same problem Judith 
has now. It looked like Skype locked the sound 
device but I did not have a closer look (and as I
say, I cannot reproduce the problem anymore).

 
 In this system, ringing is directed to the 
 default device, which is an alias for the 
 on-board Intel sound.  Sound-in and sound-out 
 use a USB-audio adapter and headset.
 
 If Judith\'s system uses the same device for 
 sound-out and for ringing, an incoming Ekiga 
 connection during a Skype conversation would be 
 problematic.

I understand Judith has the same problem as I
mentioned above...

 
 Conclusion: separate hardware for sound out and 
 for ringing is a worthwhile small investment.

A soundcard with hardware mixing could be another 
HW-based solution. Many cheap second-hand pieces 
are around. 

Palo

 
 Regards,   ... Peter E.
 
 -- 
 http://members.shaw.ca/peasthope/
 http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): Audio-Problems

2008-12-31 Thread Palo S .

 In Debian Lenny on both a generic machine and 
 an IBM NetVista, Ekiga and Skype tolerate each 
 other.  They can not use the sound hardware 
 simultanously of course but there should never 
 be a reason to.

Hm, I cannot reproduce the problem anymore. I remember
that the last time I used Skype (was some 2-3 months
ago!) Ekiga audio did not work when Skype was
running. I think it was with older versions of all 
Ekiga, Skype and operating system (Fedora). So I 
won\'t be of any help with this. Maybe Judith can 
provide information about her problem?

Palo

 
 What system is the conflict observed in?  
 Does a conflict exist immediately after startup? 
 Does a conflict only occur after a Skype conversation?
 
 Regards,... Peter E.
 
 -- 
 http://members.shaw.ca/peasthope/
 http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Audio-Problems

2008-12-30 Thread Palo S .


 It shouldnt be skype. I need both programs. After restarting it was 
 working again.

Then you should maybe complain to Skype developers?
It looks like Skype is blocking Ekiga, not the other 
way around. It works in the same way for me too, I 
have to quit Skype otherwise audio in Ekiga does not 
work. (For me it is no problem, I use Skype rarely.)



__
http://www.inzeraty.sk/ - Bezplatná inzercia v najobľúbenejších kategóriách


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-30 Thread Palo S .



- 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 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...
  weird.
  
 
 This is quite an interesting question.
 
 I must admit I\'ve seen myself the same issue you reported: my ekiga 3
 not being able to accurately display presence for my contacts in the
 long run.

Well, the issue that I reported causes more important
problem - it is not possible to reach the client after
some time (ie no incoming calls because server rejects them
although outcoming work just fine). And this is something 
I thought people would notice and report... However, wrong 
presence indication accompanies this issue so maybe you 
actually do suffer by the same problem? It is easy to see 
in the logfile: after some time there are no messages at 
all. Also, the client cannot be closed properly then.

 
 Why I did not reported this? My packs are not latest stable version, I
 did not have something more accurate than just I can see it did not work
 all time. In short, I did not believe I had enough to track the bug down
 efficiently. And I also admit my commitment to this project is sometime

I also noticed more issues but did not report from the
same reasons. Presence indication not working correctly 
after some time was the first I noticed. Then there is 
video not transmitted when using theora codec in certain 
cases, h264 not initialized correctly in certain cases, 
occasional hang of Ekiga when releasing the call...
However these issues are clearly not that important and
not so reproducible as the one that I reported.

 weaker... Let\'s no fall in the mistake of being guilty, but when
 comparing to other similar projects backed by profit, it is quite
 depressing.

Yes, this is clearly a problem. However, I have been using 
Ekiga 2 for some 2 years for calls with relatives without any 
major problems and I can say that in my experience and for my 
purposes it worked significantly better than Skype. And
Ekiga 3 is close to fix the remaining smaller problems or
missing features I had with 2 (such as cpu getting to 100%
with video or missing presence indication). So the state
of Ekiga is clearly not that depressing. Given the very limited
manpower and free time based development it is actually
unbelievable how reliably Ekiga worked for me in the last
years. Now with 3.0 and new server more issues emerged
and your questions about how these could be prevented
are of course very important to ask.

 
 This also raise question about the quality process for Ekiga. I do not
 count much on our users to perform such testing by themselves, except
 for obvious bugs like craches, totally broken feature, etc. Fortunately
 there is people like you taking time to report, but this is not the
 right way for most people who need a lot of guidance for it and who
 probably do not have the culture background to clearly see how much
 feedback is important for us.
 
 I congrats you for being so insistant on this issue. Most people would
 have given up a long time ago.

Well, suddenly my relatives started to complain that they
cannot call me and I also noticed I could not call them
sometimes. That was enough to convince even a lazy man 
like me to have a closer look and report my findings :)

 
 I think we should improve this part of our practise:
 http://wiki.ekiga.org/index.php/Pre-release_test
 
 And I also need to set back up the daily snapshots/last stable for
 Ubuntu. So many work to do...
 
 I think we should:
 1- ease the process of reporting issues; waiting for people to show up
 in the right place, then asking for a -d 4 probably make it harder to
 report.
 2- build up automatic testing/regression test for ekiga

I am sure both these points would help a lot. Regarding
1, I can think of several improvements (note that I am
not Ekiga developer so some of these may be wrong/
not possible/not feasible etc):
a) It should be possible to send the data from crash directly 
to Ekiga developers with one click. Similar thing as eg
Firefox handles this. Maybe it is already intended but when 
I get a crash, I only get the possiblity to save the log and
send it to an email address - hard to imagine that a usual
user would do that.
b) There could be an option in the GUI to deal with problems
and their reports. This would enable the user to turn on/off
log catching and in case it is turned on, to send it as
well as the report directly from the client.

Regarding 2, certainly something that would be very useful.
It could certainly not catch all the possible problems
but could still help a lot. At the beginning, something
simple like automatic periodic trunk/stable

Re: [Ekiga-list] 473 Filtered destination

2008-12-30 Thread Palo S .

 
 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 while it used to be maybe 40M at
this time with 500 and 501 in contact list.
I still cannot confirm with 100% though, I will try
on another computer and for longer time and let you
know.

Palo



__
Mobilné telefóny v slovenskej premiére a najaktuálnejšie informácie - 
http://mobil.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-30 Thread Palo S .



- 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 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 while it used to be maybe 40M at
  this time with 500 and 501 in contact list.
  I still cannot confirm with 100% though, I will try
  on another computer and for longer time and let you
  know.
  
 
 There is a bug in Asterisk on ekiga.net, I need to find a workaround
 tonight. I don\'t think Ekiga is faulty there.

I was suspecting it could be ekiga.net issue again
a.o. because I started to use Ekiga 3.0 longer time 
ago and this problem only appeared relatively recently.
Very good that finally we are getting close to the 
problem localization!

Palo

 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-29 Thread Palo S .

 
 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 till 23:18 when I quit
Ekiga (well, I had to kill it)

I am really wondering about my 100% reproducibility
on other machines and in other networks. Why does 
nobody else complain about this then? Could it be
distribution specific from some reason? There is 
Fedora 8, 9 or 10 running on all these machines 
(and the problem is also reproducible with Ekiga 3 
from Fedora 10 repositories) 

At the moment I workaround it by a script that kills 
Ekiga if the log file has not been modified for some
time...

Palo



__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-28 Thread Palo S .

   
   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


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-28 Thread Palo S .

 
 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 (although it looks more like _any_ communication
between the client and server suddenly stops, not just 
registering - have a look at the log I attached previously).

This behaviour is the same and always reproducible in 
3.0.1 and trunk and on all 4 computers at 3 different
locations that I have tested so far. The time after which 
this happens differs but seems to be between 50-100 minutes.

Palo



__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-27 Thread Palo S .

 
 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, 
Ekiga::ServiceCore, unsigned) (sip-endpoint.cpp:131)   
 
==27759==by 0x8163402: opal_init(Ekiga::ServiceCore, int*, char***) 
(opal-main.cpp:117)   
==27759==by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) 
(engine.cpp:222)  
==27759==by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230)   
   
==27759==by 0x80D6D09: main (main.cpp:4476)
==27759==  Address 0x0 is not stack\'d, malloc\'d or (recently) free\'d
==27759==
==27759== Process terminating with default action of signal 11 (SIGSEGV)
==27759==  Access not within mapped region at address 0x0
==27759==at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager, 
Ekiga::ServiceCore, unsigned) (sip-endpoint.cpp:131)
==27759==by 0x8163402: opal_init(Ekiga::ServiceCore, int*, char***) 
(opal-main.cpp:117)
==27759==by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) 
(engine.cpp:222)
==27759==by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230)
==27759==by 0x80D6D09: main (main.cpp:4476)

Palo



__
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-26 Thread Palo S .

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


__
http://auto.sme.sk - Všetko o autách (novinky, testy, autosalón, autoškola, 
porovnaj si auto)

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-26 Thread Palo S .

 
 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 the same behaviour.
I will set it to 3600 in the client and we shall see...

Palo



__
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-26 Thread Palo S .

 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?

Palo



__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-26 Thread Palo S .

 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
gconf settings were applied with delay. I tried both
3600 and 600 but the problem persists with the
same behaviour - all communication is halted after
some time. 

The network consists of Zyxel ADSL modem bridged to 
WRT54GL router running Tomato firmware. Using or not 
using port forwarding does not play a role either.
Full log using registration time of 600 is here:
ftp://quacka.no-ip.org/pub/ekiga.log.7z
(.tgz is available at the same location if preferred)

It could still be a NAT issue but it would be bit weird 
because there is a SIP hardphone connected to the same
router and it works without any problems with two SIP 
(non-Ekiga) accounts... so I really don\'t know what is
going on here at the moment!

Palo



__
http://www.pnp.sk -  pridajte svoje fotky na PaciNepaci


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-25 Thread Palo S .
 
 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 to reproduce the problem and get his log later.

However, I am wondering now. How often should the 
registration renewing happen? I just looked to my current
Ekiga log and there is absolutely no message between
4:47 till 14:13. And the 14:13 message only appeared 
because I wanted to close Ekiga - which did not succeed
(it hanged, I had to kill it). I don\'t know whether this 
is related to the issue we have in this thread... anyway 
the log is here (although I don\'t think it says much, I 
cut it to the last 100 lines)
ftp://quacka.no-ip.org/pub/ekiga_last100.log

Palo



__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-25 Thread Palo S .


 
 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 claims it is
registered and I can even make a call, however I am
not reachable - the other side gets \408 Request
timeout\. Trying to quit the client causes a freeze
then. It is 3.0.1 compiled from source.

I will try to play with NAT settings when I have some 
time to see whether it is caused by that.

Palo



__
Sprievodca herným svetom - http://hry.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] 473 Filtered destination

2008-12-24 Thread Palo S .


 
 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 destination already detected as unresponsive.
 
 I have disabled it.

Great, thanks! So one reason of the inability to make calls
should be gone now, however doing today\'s Christmas calls,
I found myself again not able to make a call and this time
Kamailio returned \480 Offline\ (repeatedly). I am sure 
though that the other side was online and registered because 
I again watched it via VNC. I have the logfile from the caller 
but I was not able to say more from it:
ftp://quacka.no-ip.org/pub/ekiga.log
Maybe a log from the called side would say more but I don\'t
have that. The problem was fixed by restarting Ekiga on both
sides...

At least one thing makes sense now: I mentioned that 
sometimes restart of Ekiga fixes the problem and sometimes
not - then it disappears by itself after some time.
Now it becomes very likely that the former corresponds 
to 480 Offline and the latter to 473 Filtered destination
(from openSER list I found that once blacklisted, the
server always returns 473 for limited amount of time)

Palo



 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
Mobilné telefóny v slovenskej premiére a najaktuálnejšie informácie - 
http://mobil.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-12-23 Thread Palo S .

I can confirm that this problem is fixed. The call is not 
canceled anymore (although I only tested via VNC ie nobody
on the other side so I cannot say whether there are some 
other issues such as voice not coming through).
Good job!

Palo


- Originálna Správa -
Od: Damien Sandras  
Komu: Ekiga mailing list  
Poslaná: 21.12.2008 10:31 
Predmet: Re: [Ekiga-list] \\\remote user cleared the call\\\ problem

 Le samedi 20 dĂŠcembre 2008 Ă  20:33 +0100, Palo S. a ĂŠcrit :
A fix has been put into the stable branch and into TRUNK. Is that
something you can test ?
   
  
  Tried to test snapshot from 18th and 19th but none of them
  compiled. The (first) error message was:
  
  ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member function 
  `virtual void Opal::Sip::EndPoint::fetch(std::string)\\\':  
 
  ../../../../lib/engine/components/opal/sip-endpoint.cpp:313: error: 
  `Dialog\\\' is not a member of `SIPSubscribe\\\'
  
  Can you please let me know which code can I use for testing.
  
 
 You need the latest TRUNK for opal, ptlib and ekiga. Please note that
 lastest TRUNK is broken with video.
 
 If you want something stable, I would suggest to follow this:
 http://wiki.ekiga.org/index.php/SVN
 (and use the gnome-2-24 instructions)
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-12-20 Thread Palo S .

  A fix has been put into the stable branch and into TRUNK. Is that
  something you can test ?
 

Tried to test snapshot from 18th and 19th but none of them
compiled. The (first) error message was:

../../../../lib/engine/components/opal/sip-endpoint.cpp: In member function 
`virtual void Opal::Sip::EndPoint::fetch(std::string)\':
 
../../../../lib/engine/components/opal/sip-endpoint.cpp:313: error: `Dialog\' 
is not a member of `SIPSubscribe\'

Can you please let me know which code can I use for testing.

Palo


 Sounds good! I should be able to test it within a few days.
 Of course I\\\'ll post the results here as soon as I have them.
 
 Palo
 
  --
_ Damien Sandras
  (o-
//Ekiga Softphone : http://www.ekiga.org/
  v_/_   Be IP   : http://www.beip.be/
 FOSDEM  : http://www.fosdem.org/
 SIP Phone   : sip:dsand...@ekiga.net
 
 
   ___
  ekiga-list mailing list
  ekiga-list@gnome.org
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 
 
 __
 http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://zabava.sme.sk/ - Stránka čo usmeje ti tvár


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net?

2008-12-14 Thread Palo S .



- Originálna Správa -
Od: Colin Alie  
Komu:  
Poslaná: 13.12.2008 23:59 
Predmet: Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatible 
withekiga.net?

 Good evening,
 
 You\'re correct Palo.  It was Damien who suggested upgrading to version 3.0.  
 Sorry for the confusion and thanks for the continuing to follow this thread.
 
   Can you have a look at the port forwarding on your router, especially port 
 5060? In my case disabling port forwarding of 5060 did the trick...
 
 By \disabling port forwarding of 5060\, are you suggesting that I disable 
 forwarding of incoming packets to port 5060 on the external interface of my 
 modem/router to port 5060 of the laptop upon which Ekiga is running?
 
 At the moment, there are no port forwarding rules in place.

Hi Colin,

which router do you use? Just wondering that some routers do 
some kind of 6050 mapping automatically and you can\'t see it 
in port forwarding options, Speedtouch 510/530 being a well
known example...
If this is not the case, perhaps you can try to forward 6050
to your notebook (this is just a blind attempt, of course,
as the opposite helped in my case - but still may be worth 
a shot since we have reasons to believe that Kamailio has 
problems with your current NAT settings)

Palo


 
 Until next time, Colin.
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net?

2008-12-13 Thread Palo S .

 Palo, as per your suggestion, I upgraded to Ekiga 3.0.  However, I\'m still 

I don\'t think it was my suggestion, anyway good that you
tried it. Now after looking at your log I can bet that your 
issue is the same as I had in \'remote user cleared the call\' 
since Kamailio does exactly the same thing - from some
reason it sends CANCEL on your behalf right after the call 
has been estabilished. (Also, I remember when I tried Ekiga 
2, it resembled your problem with Ekiga 2). 

So we can be fairly certain to say it is a NAT related bug 
in Kamailio. You can still try to workaround it in a similar
fashion as I did. Can you have a look at the port forwarding
on your router, especially port 5060? In my case disabling
port forwarding of 5060 did the trick...

Palo



__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-12-11 Thread Palo S .
 
 I wonder if we should just not ignore the cancel...
 -- 

It seems that proper fix should be done on Kamailio.
Ignoring CANCEL for INVITE could be a workaround in 
the meantime, however it would probably cause 
problems in situations when invite should be cancelled 
(ie when the other side cancels indeed or in case
of multiple branches)?

Palo



__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-12-11 Thread Palo S .

 
 Not sure how to fix Kamailio

It may be possible for Kamailio developers to 
identify place (in the code) where Kamailio
sends this CANCEL by itself and fix...

 but I wonder if the CANCEL is not taken
 into account when it should not be.

I think that Ekiga does it correctly, at least
I can\'t see why should it not take it into 
account. If there is a safe way to distinguish 
between \correct\ and \incorrect\ CANCEL then 
of course, however I don\'t know how that could
be done

Palo


 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:dsand...@ekiga.net

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatiblewith ekiga.net?

2008-12-07 Thread Palo S .

This looks like a NAT issue. You can have a look
at the \remote user cleared the call\ thread that
I opened in November - that is another example 
when the NAT settings that worked with the old
server stopped working with the new one. Maybe 
a change in NAT settings could fix your problem
as it was in my case. (I still did not find time
to run a sniffer to find out what exactly was going 
on there)

Palo



__
http://www.pnp.sk -  pridajte svoje fotky na PaciNepaci


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-12-02 Thread Palo S .

 
 A cancel can be sent if you are using forking, ie 2 Ekiga registered
 with the same account name, from 2 different IP addresses and ports. As
 soon as one answers, a CANCEL is sent to the other one.
 
 Couldn\'t it be the case ?

It could be that due to a problem with NAT a private
IP communicates with the server as well as the public 
IP. I can probably only say after I sniff the 
communication. I will run a sniffer when I have time 
and let you know if I find something interesting. It 
is also interesting that with Ekiga 2.0.12 (on called 
side) it behaves differently - I have not had a look 
at d4 yet but it looked like caller (thought that) 
estabilished a SIP connection but called side not 
(it continued to ring on the called side, even after 
cancelling the call on the caller side). 

In any case, it worked fine with the previous server, 
so there must be a way to either fix or at least 
workaround the problem on the code level (either server
or maybe also client) which would be nice at least because 
of ordinary users that do not know/wish to play around 
with port forwarding (all ports forwarding was 
originally enabled by the provider in this case, not by 
the user...)

Palo


 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje 
myšlienky, zážitky a nové informácie - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-11-30 Thread Palo S .
 
 It looks like a bug on Kamailio (the SIP Router). Because called
 receives a CANCEL message, but caller does NOT send a CANCEL message.

Indeed - I did not notice this.
It is true that the problem emerged around the time
when Kamailio started to be used.

 I\'m not sure how to fix that :-/

The question is why does it happen on one machine
but not on some others? I am not aware of anything
specific about this machine, it runs the same system,
and Ekiga compiled in the same way as on a system
that does not suffer by this. So my best guess is
that it could be network/router specific. I will
try to play a bit with the network settings 
(especially NAT) and see.

 
 Is that 100% reproducable ?

So far I had 100% \success\ rate (maybe 20 attempts
in several days)...

Palo



__
BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje 
myšlienky, zážitky a nové informácie - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] \remote user cleared the call\ problem

2008-11-30 Thread Palo S .

The problem disappeared after I disabled forwarding
of 5060 to the called machine. So yet another NAT
issue. However the port forwarding was set a long 
time ago and the problem only appeared recently, 
confirming that the new Ekiga server was the trigger
of the problem. It would be nice if Kamailio could
handle the network settings that the previous server
did but I am not sure whether somebody wants to look
at this - if so, then I can provide any information
required.

Palo



__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] [Fwd: AW: [Fwd: h264 bug]]

2008-10-27 Thread Palo S .

Hi Matthias,

thanks for the message! It can easily be a kernel 
issue since the computer on which it works is 
running a different kernel from the other two: 
it works under 2.6.23.1-42.fc8.i686 and does not 
work under 2.6.25.6-55.fc9.i686 (I don\'t have
access to the second computer that suffered by
the problem at the moment but it runs F9 with
either 2.6.25 or 2.6.24).

However it does not seem that AppArmor patches 
could be on blame since both suffering machines 
are stock Fedora kernels and I doubt that these 
come with any AppArmor patches. SELinux is 
disabled on all these machines.

I\'ll try to confirm whether it is a kernel issue 
and if so to narrow it down, I will post my
findings here soon!

Palo



- Originálna Správa -
Od: Damien Sandras  
Komu: \Palo S.\  
Poslaná: 27.10.2008 09:26 
Predmet: [Fwd: AW: [Fwd: [Ekiga-list]  h264 bug]]

 
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   Be IP   : http://www.beip.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 
 
 
  --- Begin of attached message ---
 
 From: Matthias Schneider 
 To: Damien Sandras 
 Date: 2008-10-27 08:36:12
 
 If you can forward to Palo S. (I just subscribed to user ML)
 
 Hi Palo,
 
 this issue has been reported by another person as well, 
 and it seems to be an issue of some kernel modifications.
 It is suspected (although not yet proben) that AppArmor
 patches to the kernel are responsible for this behaviour
 (I suspect a bug there). 
 So it would be interesting to know what kind of kernel you 
 are using on the setups that do produce the error and on the
 system where it works.
 
 Matthias
 
 
 
   
  --- End of attached message ---
 
 


__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] h264 bug

2008-10-26 Thread Palo S .
I can reproduce the h264 bug on another machine.
Also I found that it was reported several months 
ago here:
http://www.mail-archive.com/ekiga-list@gnome.org/msg04168.html

Damien, apparently H264 is not stable but it also
looks like there is nobody to maintain/fix the bugs 
in it, so probably H264 should be disabled by default?
(It is very nasty bug since not only H264 does not work
but also Ekiga becomes unresponsible and slowly eats
all memory!)

Palo



- Originálna Správa -
Od: Palo S.  
Komu:  
Poslaná: 23.10.2008 17:18 
Predmet: [Ekiga-list] h264 bug

 
 When trying to make a call using h264 codec, Ekiga
 freezes, the image is not transferred to the remote
 and Ekiga slowly eats all the memory. The -d 4
 log keeps repeating:
 
 h264pipe_unix.cxx(234)  H264IPC PP: Failure on reading - terminating
 h264pipe_unix.cxx(221)  H264IPC PP: Error when closing UL named pipe
 h264pipe_unix.cxx(236)  H264IPC PP: Received EOF - terminating
 h264pipe_unix.cxx(242)  H264IPC PP: Bad flag set on writing - terminating
 ...
 h264pipe_unix.cxx(248)  H264IPC PP: Bad flag set on flushing - 
 terminating
 h264pipe_unix.cxx(234)  H264IPC PP: Failure on reading - terminating
 h264pipe_unix.cxx(236)  H264IPC PP: Received EOF - terminating
 ...
 
 The complete log can be found at
  ftp://quacka.no-ip.org/pub/log_full
 However, it is 30 MB most of which are just the
 error message above repeating so there is also
 the first MB only in
 ftp://quacka.no-ip.org/pub/log_head
 
 Always reproducible...
 
 
 
 
 __
 http://sport.sme.sk - Najkomplexnejšie informácie zo športu
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] h264 bug

2008-10-26 Thread Palo S .

 
 The fact that you have a problem with H.264 while nobody else seems to
 have one doesn\'t mean that it is unstable and should be removed.

Sorry if it sounded rude - it was just a suggestion
of course. It was not to remove it but just to disable 
by default and not because of me but because it was
reported half a year ago and nobody seemed to be 
able to do anything with it - and now again nobody
seems to be able to do/suggest anything which means
that it may reside in Ekiga for quite long and drive
some users off. I am sure that if there are two users 
that report it then there are thousands of others who 
just try Ekiga and say it does not work - which I just 
meant to prevent.

Anyway, if you think that nobody else has the problem 
then I shut up!


 
 How did you install it ?

I installed 3.0.1 from source, x264 and ffmpeg are from 
livna. Both theora and H261 work fine, just H264 is broken. 
The behaviour is exactly the same on both machines where 
the problem occurs and the same as in the report from May 
from the other user...

Strangely enough, it works on a third machine where
I installed it in exactly the same way, using the same
ffmpeg and x264 from livna! That means that the problem
is not in incorrect installation or in x264 version but
probably a specifically activated bug in Ekiga (or 
libraries it uses)... I was hoping that somebody could 
point where could be the problem...




__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] additions to wiki

2008-10-23 Thread Palo S .
Yesterday I reported here a few issues I had with 3.0.1
and it turned out that some of them were related to
the compile time configuration. I thought it may be a good
idea to add this information to wiki (faq or additional
information)?

1. The problem with webcam not working has been solved
by using --enable-v4l for ptlib configure script. THere
is a lot of v4l only webcams which simply would not work
with default ptlib configuration so this option is 
essential for these

2. The problem with missing presence indication has
been solved by installing expat-devel (expat is an
XML parser and the header files were required so that
ptlib/opal can use vxml which seems to be required for
presence indication). This is even less obvious than
the previous v4l case and I was not able to find this 
information anywhere, including nobody suggesting this 
in Ekiga list. 
(Eugen, is this your problem too or is your presence
indication problem caused by something else?)

Of course all of this is only relevant to those who 
compile Ekiga from source (but may cause the problems
for binaries if packager was not aware of this or
did not want to support this!)



__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] h264 bug

2008-10-23 Thread Palo S .

When trying to make a call using h264 codec, Ekiga
freezes, the image is not transferred to the remote
and Ekiga slowly eats all the memory. The -d 4
log keeps repeating:

h264pipe_unix.cxx(234)  H264IPC PP: Failure on reading - terminating
h264pipe_unix.cxx(221)  H264IPC PP: Error when closing UL named pipe
h264pipe_unix.cxx(236)  H264IPC PP: Received EOF - terminating
h264pipe_unix.cxx(242)  H264IPC PP: Bad flag set on writing - terminating
...
h264pipe_unix.cxx(248)  H264IPC PP: Bad flag set on flushing - 
terminating
h264pipe_unix.cxx(234)  H264IPC PP: Failure on reading - terminating
h264pipe_unix.cxx(236)  H264IPC PP: Received EOF - terminating
...

The complete log can be found at 
ftp://quacka.no-ip.org/pub/log_full
However, it is 30 MB most of which are just the
error message above repeating so there is also
the first MB only in
ftp://quacka.no-ip.org/pub/log_head

Always reproducible...




__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] additions to wiki

2008-10-23 Thread Palo S .

 
 I modified two pages on wiki about this issue (see 
 http://wiki.ekiga.org/index.php/Special:Recentchanges).  Maybe disabling 
 it by default is not in the end such a good idea...
 
 libexpat1-dev is in the Build-Depends field for debian (ubuntu too I 
 suppose) packages.  I have just added it too to the wiki.
 

Great, thanks! I am sure it will help a few people.
I don\'t know why v4l is disabled by default but I
guess they have their reasons for that... Good 
that Ubuntu/Debian don\'t suffer by the presence 
indication issue, hopefully other distros do not
too.

Palo




__
Sprievodca herným svetom - http://hry.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] a few problems with 3.0.1

2008-10-22 Thread Palo S .
 
 Did you try installing the ptlib-plugins-v4l (or some similar name)
  package which provides the V4L plugin driver?

I compiled from source, but I have now sorted this 
out - it was caused by opal configure script which 
only enabled v4l2 support by default - simply 
providing --enable-v4l did the trick... shame on me,
I  should have checked this before! My only excuse
is that this manual specification was not required 
when I compiled Ekiga previously...
Update: now I see that in the meantime Eugen already 
has mentioned this too!

 
  2. The presence indication does not work for any
  of my ekiga contacts, including echo test and
  conference room - all are displayed without any
  presence indication (ie the same as \\\IPBX\\\
   contacts on this screenshot:
   http://blog.ekiga.net/?p=61)
 
 Are your registered to ekiga.net ?

Yes, of course. I am registred, I can make a call
(now including video part!) etc. Just no presence
indication. Is there another option required at
compilation time? Or is it a bug?

 
  3. Microphone does not work with \\\Default (PTLIB/ALSA)\\\,
  however it works with \\\HDA Intel (PTLIB/ALSA)\\\
   specified...
 
 Then that works...

In principle yes but is it ok if default does not work? 
What could be the reason?

 
 I\\\'m annoyed by point 5 -- but I\\\'m not sure the bug is on our side.

I was thinking it was not on Ekiga side. However now 
I am bit puzzled because I just tested that other GTK+ 
applications work fine. I am posting the error message:

The program \\\'ekiga\\\' received an X Window System error.
This probably reflects a bug in the program.
The error was \\\'BadAlloc (insufficient resources for operation)\\\'.
  (Details: serial 42 error_code 11 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x440007b unexpectedly destroyed

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400080 unexpectedly destroyed
^@
(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400083 unexpectedly destroyed

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400084 unexpectedly destroyed

(ekiga:3734): GLib-GObject-WARNING **: invalid uninstantiatable type `\\\' in 
cast to `GtkWidget\\\'

(ekiga:3734): GLib-GObject-WARNING **: invalid uninstantiatable type `\\\' in 
cast to `GObject\\\'

(ekiga:3734): GLib-GObject-CRITICAL **: g_object_get_data: assertion 
`G_IS_OBJECT (object)\\\' failed

Segmentation fault


It seems that the last error message actually changes,
I can also get
(ekiga:3916): Gtk-CRITICAL **: gtk_style_detach: assertion `style-attach_count 
 0\' failed
(ekiga:4687): Gtk-CRITICAL **: gtk_widget_realize: assertion 
`GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)\' failed
Gtk:ERROR:(gtkwidget.c:7942):gtk_widget_real_map: assertion failed: 
(GTK_WIDGET_REALIZED (widget))
Aborted

etc

I am not sure how much useful this is and what to do
to get a better error description? -d 4 does not seem
to be useful and I did not succeed to run ekiga with
gdb



__
Svetova kniznica SME - literarne klenoty 20. storocia - http://knihy.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] a few problems with 3.0.1

2008-10-21 Thread Palo S .

Hi everybody,

I have compiled and tested 3.0.1 today and here is 
a few problems/comments/questions that I have.
The test machine was Fedora 9, 2.6.25.6-55.fc9.i686
kernel.

1. My webcam does not work with Ekiga 3 although it
works just fine with Ekiga 2 (and works fine with
basically any other program I tried - mplayer, vlc).
It is Labtec Webcam Pro using the gspca driver. I
think that the problem is that Ekiga detects the
device as V4L2, however it is V4L. It does not work
as V4L2 under other programs too. With Ekiga 2 I
could choose V4L or V4L2 as video plugin, however 
with Ekiga 3 this does not seem to be possible 
anymore and the automatic detection only provides 
V4L2... Any way to force V4L?
(error message:
Error while accessing video device /dev/video0
There was an error while opening the device. 
...)

2. The presence indication does not work for any
of my ekiga contacts, including echo test and
conference room - all are displayed without any
presence indication (ie the same as \IPBX\ 
contacts on this screenshot: 
http://blog.ekiga.net/?p=61)

3. Microphone does not work with \Default (PTLIB/ALSA)\,
however it works with \HDA Intel (PTLIB/ALSA)\ 
specified...

4. At opal compilation, there is a new dependency
which is not taken into account by configure,
namely swig (compilation stopped with an error message
and continued after I installed swig - so no big problem
but it should be checked by configure I believe?)

5. This one is just an information if somebody gets 
into the same issue: originally I reproducibly got 
a segfault if I wanted to make a call and the 
following error message appeared if ekiga --sync was 
run (followed by an attempt to make a call):
Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE 
(drawable)\' failed 
It turned out that this was an issue between GTK+ 
and KDE4 desktop efffects - after KDE4 desktop
effects were turned off, the problem disappared.

6. Although I did not get a chance to use video, I 
have noticed that the \side by side\ view option is 
no longer available. Is there a plan to include it
again? Basically all people I talked to prefer
this over PIP/no local because one can both see
himself and it does not cut from the remote at
the same time - for some it was one of the 
\killer features\ of Ekiga, I believe!

I would be glad for any comments. Also, could 
a developer please let me know if (s)he thinks 
that any of these should be filed as a bug?



__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] PBoolean snapshot compilation problem

2008-09-07 Thread Palo S .

Successfully compiled the latest ptlib and opal snapshots
but the following error appears when trying to compile 
ekiga snapshot:
error: \'PBoolean\' has not been declared
error: \'PBoolean\' does not name a type
(and repeating many times)
Does anyone know what\'s going on here? I tried the 
--disable-ansi-bool option but does not seem to help...




__
http://www.inzeraty.sk/ - Bezplatná inzercia v najobľúbenejších kategóriách


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] PBoolean snapshot compilation problem

2008-09-07 Thread Palo S .

  Successfully compiled the latest ptlib and opal snapshots
  but the following error appears when trying to compile 
  ekiga snapshot:
  error: \\\'PBoolean\\\' has not been declared
  error: \\\'PBoolean\\\' does not name a type
  (and repeating many times)
  Does anyone know what\\\'s going on here? I tried the 
  --disable-ansi-bool option but does not seem to help...
  
 
 You probably have a mix of old and new ptlib/opal headers on your
 system.

Yes indeed - there was a single header file forgotten from 
previous installation... thanks for advice! I double-checked 
there were no other forgotten headers and compiled from scratch
again and Ekiga compiles now - but does not run (segfault).



 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   NOVACOM : http://www.novacom.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list


__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] PBoolean snapshot compilation problem

2008-09-07 Thread Palo S .

 Just post a backtrace somewhere, but it is certainly the same kind of
 problem.

I believe I really deleted all the old versions...
I put the trace to ftp://quacka.no-ip.org/pub/gdb-ekiga.txt
It does not say much to me, unfortunately.


__
http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] PBoolean snapshot compilation problem

2008-09-07 Thread Palo S .


 Your glib is not up to date. It should not run correctly when commenting
 out that line.
 

Indeed, glib is not up to date. But I believe it should
not cause much trouble.
I understand that this code is only used for STUN 
detection and since I chose to use previous settings 
this code was probably never performed.

  2) not very nice default settings: the audio devices were 
  set to SILENT, the video bandwidth to 1 Mbps 
  (unrealistically high for a typical user)
 
 The default value is Default (PTLIB/Alsa) for the audio devices and 48
 kbits/s for the video bandwidth.
 If you have a different default value, then your GConf installation is
 broken.

Can be. I don\'t know how can I check that gconf is broken.
(If I need to use gconf occasionally it works ok so
it is not broken completely at least)

  
  3) missing some nice functionalities from Ekiga 2: 
  a. sound configuration test in the configuration manager
 
 Will not reappear. Testing should be done with [EMAIL PROTECTED], we will
 improve the setup on ekiga.net itself.

OK. I personally liked the possibility to check the sound
configuration independently from network but certainly one
can live without it.

  
  b. sound settings and status in Ekiga GUI
 
 It is still there. (See Call Panel)

Indeed, my mistake, sorry for that one.

 
  c. option to disable video
 
 Just disable all video codecs.

OK. This worked. 

 
  4) the echo test results - there is a delay of several 
  seconds. Furthermore, the sound chops frequently. This
  happens also if I set the video to logo (completely 
  disabled seems not to be in the GUI - point 3c). 
  Hardly usable because of this.
  
 
 Using PCMU / PCMA as codecs ?

PCMU. The problem persists when video is disabled.
The chopiness seems to be resolved by increasing 
the jitter to ~500 ms (however, with Ekiga 2 
jitter of ~100-150 ms works fine). 

Palo


 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   NOVACOM : http://www.novacom.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 


__
BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje 
myšlienky, zážitky a nové informácie - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Is the ekiga stun server down?

2008-08-27 Thread Palo S .

All is up again now.




__
http://cestovanie.sme.sk/ - Celý svet na vašom monitore


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Is the ekiga stun server down?

2008-08-26 Thread Palo S .


I am afraid that not only the STUN server but the whole
ekiga.net has problems since just replacing STUN server 
did not connect me to Ekiga network (either from Ekiga 
or Twinkle client) and www.ekiga.net is down too...



__
Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-devel-list] [Ekiga-list] Ekiga 3.00 available for WIN32 *only*

2008-04-01 Thread Palo S .

Excellent news! I completely agree with this move - you
discovered a hole in the market! There is just too much 
competition in VOIP under Linux while in fact all the 
Windows users just use one (rather crappy and limited) 
piece of software - apparently nothing better is available. 
Thus, I am absolutely sure that immediately after the 
release of Ekiga 3.0 for Windows, the majority of Windows 
users will adopt 3.0 because no current software for Windows
can even touch the functionalities and capabilities of
Ekiga 2, not talking about 3. 
The only major objection I have is that you should be more
looking into future and not release WIN32 but rather WIN128. 
This new platform is going to dominate the world in the 
coming centuries and it would be a pity if Ekiga lost this 
market just because it concentrates on the old WIN32.
So: release Ekiga 3 for WIN128 only and as shareware only
and the success is inevitable.




- Originálna Správa -
Od: Damien Sandras  
Komu: Ekiga mailing list , ekiga-devel-list  
Poslaná: 01.04.2008 21:57 
Predmet: [Ekiga-list] Ekiga 3.00 available for WIN32 *only*

 Hello,
 
 I just put the news on http://www.ekiga.org :
 
 Due to the big popularity of the Microsoft Windows operating system
 compared to the GNU/Linux desktop, we have decided to put all our
 efforts on the WIN32 port of Ekiga.
 
 Due to the increased amount of work and the lack of spare time, Ekiga
 3.00 will only be released for WIN32.
 
 While Ekiga 3.00 will stay free (as free beer), it will be the last
 version to be completely free. From Ekiga 3.20, Ekiga will become a
 shareware with a small license fee to use either Ekiga or its associated
 platform Ekiga.net. The money that it will generate will finally allow
 us to live from our project instead of spending countless hours for free
 on it.
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   NOVACOM : http://www.novacom.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 ___
 ekiga-list mailing list
 [EMAIL PROTECTED]
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-list] Ekiga 3.00 available for WIN32 *only*

2008-04-01 Thread Palo S .

Excellent news! I completely agree with this move - you
discovered a hole in the market! There is just too much 
competition in VOIP under Linux while in fact all the 
Windows users just use one (rather crappy and limited) 
piece of software - apparently nothing better is available. 
Thus, I am absolutely sure that immediately after the 
release of Ekiga 3.0 for Windows, the majority of Windows 
users will adopt 3.0 because no current software for Windows
can even touch the functionalities and capabilities of
Ekiga 2, not talking about 3. 
The only major objection I have is that you should be more
looking into future and not release WIN32 but rather WIN128. 
This new platform is going to dominate the world in the 
coming centuries and it would be a pity if Ekiga lost this 
market just because it concentrates on the old WIN32.
So: release Ekiga 3 for WIN128 only and as shareware only
and the success is inevitable.




- Originálna Správa -
Od: Damien Sandras  
Komu: Ekiga mailing list , ekiga-devel-list  
Poslaná: 01.04.2008 21:57 
Predmet: [Ekiga-list] Ekiga 3.00 available for WIN32 *only*

 Hello,
 
 I just put the news on http://www.ekiga.org :
 
 Due to the big popularity of the Microsoft Windows operating system
 compared to the GNU/Linux desktop, we have decided to put all our
 efforts on the WIN32 port of Ekiga.
 
 Due to the increased amount of work and the lack of spare time, Ekiga
 3.00 will only be released for WIN32.
 
 While Ekiga 3.00 will stay free (as free beer), it will be the last
 version to be completely free. From Ekiga 3.20, Ekiga will become a
 shareware with a small license fee to use either Ekiga or its associated
 platform Ekiga.net. The money that it will generate will finally allow
 us to live from our project instead of spending countless hours for free
 on it.
 -- 
  _ Damien Sandras
 (o-  
 //\\Ekiga Softphone : http://www.ekiga.org/
 v_/_   NOVACOM : http://www.novacom.be/
FOSDEM  : http://www.fosdem.org/
SIP Phone   : sip:[EMAIL PROTECTED]

 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Scaling video in Ekiga?

2008-01-23 Thread Palo S .

As far as I know it is almost impossible to transmit with higher
resolution than QCIF (176x144) with Ekiga 2.0.x - it is definitely
not possible to set it from the graphical interface and I actually 
did not succeed to get higher resolution even when I really tried...

I would suspect the driver could be on blame. Have you tried to
use the webcam with the \Display images from your camera\ button?
Is the problem also visible there? If the problem is not here, 
another possibility may be slow CPU, although this would also be
manifested by choppy sound. I would also try to do the echo test
to see whether the problem is there too. And if nothing helps, 
then -d 4 output could tell more...



- Originálna Správa -
Od: Ed McDonagh  
Komu:  
Poslaná: 23.01.2008 21:19 
Predmet: [Ekiga-list] Scaling video in Ekiga?

 Hi all
 
 For those who remember my requests for help in early January with
 problems calling from Windows to Linux and vice versa whilst on the same
 lan, thank you for all your help - everything worked fine once we were
 in different places. Phew!
 
 I now have a new help request.
 
 I have a 640x480 webcam built-in to my laptop running linux. My
 mother-in-law has a lower resolution webcam built-in to her laptop
 running WindowsXP.
 
 Her video looks clean and quick, with no blockyness on the default
 maximum video bandwidth. My video (from what she tells me and from using
 the 500 echo) is much slower if the Quality Setting is all the way to
 the right, and blocky as soon as you start going across to frame rate
 priority. This is the case even on higher bandwidth settings. However,
 if I don\'t move, the picture is lovely nice and sharp! Both video images
 are displayed at the same size, but the incoming \'looks\' to be lower
 resolution. 
 
 Monitoring the bandwidth usage on linux shows that the incoming data
 (her video) is much lower than the outgoing (my video), although that is
 after I have increased the max bandwidth of course!
 
 So I think that the problem must be that my webcam is transmitting video
 at full 640x480. Is this possible? Can it be downsized? 
 
 Thanks for your help.
 
 Ed
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] audio lag on 2.0.11

2007-11-16 Thread Palo S .

Indeed, I can confirm this regression. I blamed my new provider 
for this increased lag problem but now I have tried downgrading 
to 2.0.9 and indeed, the lag is significantly smaller. Possibly
important difference in -d4 logs between 2.0.9 and 2.0.11:

2.0.11:
Media   Audio sink data size set to  320 bytes and 20 buffers.

2.0.9:
Media   Audio sink data size set to  320 bytes and 3 buffers.



2.0.11:
2007/11/16 23:10:16.898   0:29.422  SIP Handler:91a1798 GMManagerWill 
establish the connection
2007/11/16 23:10:16.898   0:29.422  SIP Handler:91a1798 OpalMan 
OnEstablished [EMAIL PROTECTED]
2007/11/16 23:10:16.898   0:29.422  SIP Handler:91a1798 Call
OnEstablished [EMAIL PROTECTED]
2007/11/16 23:10:16.905   0:29.429  Media Patch:921dc90 RTP First sent 
data: ver=2 pt=PCMU psz=160 m=1 x=0 seq=23418 ts=0 src=2927315401 ccnt=0
2007/11/16 23:10:16.907   0:29.431  SIP Handler:91a1798 SIP Awaiting next 
PDU.
2007/11/16 23:10:16.920   0:29.444   RTP Jitter:92369c8 RTP First receive 
data: ver=2 pt=PCMU psz=160 m=0 x=0 seq=45837 ts=9120 src=1294607361 ccnt=0
2007/11/16 23:10:16.990   0:29.514  Media Patch:922f770 RTP First sent 
data: ver=2 pt=H261 psz=950 m=0 x=0 seq=19986 ts=0 src=2536963168 ccnt=0
2007/11/16 23:10:17.927   0:30.451  Housekeeper RTP Found existing 
session 1
2007/11/16 23:10:17.927   0:30.451  Housekeeper RTP Found existing 
session 2
2007/11/16 23:10:18.069   0:30.593  Media Patch:9220bb0 RTP Jitter buffer 
target size decreased to 160 (20ms)
2007/11/16 23:10:18.893   0:31.417  Media Patch:921dc90 RTP Transmit 
statistics:  packets=101 octets=16160 avgTime=19 maxTime=43 minTime=6
2007/11/16 23:10:18.912   0:31.436  Housekeeper RTP Found existing 
session 1
2007/11/16 23:10:18.912   0:31.436  Housekeeper RTP Found existing 
session 2
2007/11/16 23:10:18.927   0:31.451   RTP Jitter:92369c8 RTP Receive 
statistics:  packets=101 octets=16160 lost=0 tooLate=0 order=0 avgTime=20 
maxTime=28 minTime=12 jitter=2 maxJitter=4
2007/11/16 23:10:19.944   0:32.468  Housekeeper RTP Found existing 
session 1
2007/11/16 23:10:19.944   0:32.468  Housekeeper RTP Found existing 
session 2
2007/11/16 23:10:20.628   0:33.152  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:20.648   0:33.172  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:20.708   0:33.232  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:20.728   0:33.252  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:20.903   0:33.427  Media Patch:921dc90 RTP Transmit 
statistics:  packets=201 octets=32160 avgTime=20 maxTime=43 minTime=5
2007/11/16 23:10:20.920   0:33.444   RTP Jitter:92369c8 RTP Receive 
statistics:  packets=201 octets=32160 lost=0 tooLate=0 order=0 avgTime=19 
maxTime=29 minTime=11 jitter=4 maxJitter=6
2007/11/16 23:10:20.929   0:33.453  Housekeeper RTP Found existing 
session 1
2007/11/16 23:10:20.929   0:33.453  Housekeeper RTP Found existing 
session 2
2007/11/16 23:10:21.188   0:33.712  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:21.208   0:33.732  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:21.268   0:33.792  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:21.288   0:33.812  Media Patch:9220bb0 RTP Jitter buffer 
target realigned to current jitter buffer
2007/11/16 23:10:21.405   0:33.929  Media Patch:9220bb0 RTP Jitter buffer 
length exceeded
2007/11/16 23:10:21.405   0:33.929  Media Patch:9220bb0 RTP Jitter buffer 
size increased to 320 (40ms)
2007/11/16 23:10:21.749   0:34.273  Media Patch:922f770 RTP Transmit 
statistics:  packets=169 octets=130630 avgTime=40 maxTime=96 minTime=0
2007/11/16 23:10:21.959   0:34.483  Housekeeper RTP Found existing 
session 1
2007/11/16 23:10:21.959   0:34.483  Housekeeper RTP Found existing 
session 2
2007/11/16 23:10:22.900   0:35.424  Media Patch:921dc90 RTP Transmit 
statistics:  packets=301 octets=48160 avgTime=19 maxTime=60 minTime=5
2007/11/16 23:10:22.929   0:35.453   RTP Jitter:92369c8 RTP Receive 
statistics:  packets=301 octets=48160 lost=0 tooLate=0 order=0 avgTime=20 
maxTime=29 minTime=11 jitter=4 maxJitter=6


2.0.9:
2007/11/16 23:12:14.826   0:27.369  SIP Handler:a5a2fe8 GMManagerWill 
establish the connection
2007/11/16 23:12:14.826   0:27.369  SIP Handler:a5a2fe8 OpalMan 
OnEstablished [EMAIL PROTECTED]
2007/11/16 23:12:14.826   0:27.369  SIP Handler:a5a2fe8 Call
OnEstablished [EMAIL PROTECTED]
2007/11/16 23:12:14.833   0:27.376  SIP Handler:a5a2fe8 SIP Awaiting next 
PDU.
2007/11/16 

Re: [Ekiga-list] audio lag on 2.0.11

2007-11-16 Thread Palo S .

I should also add that I am not using Ubuntu but Fedora 7
so this does not seem to be packaging/distribution specific
problem. More specifically, I used these packages in the 
test:

ekiga-2.0.9-0.fc6
pwlib-1.10.7-0.fc6
opal-2.2.8-0.fc6

ekiga-2.0.11-1.fc7
opal-2.2.11-1.fc7
pwlib-1.10.10-1.fc7




__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CIF over h261 on Ekiga 2.0

2007-11-06 Thread Palo S .

 It\'s impossible, CIF is being sent... (even if the log indicates QCIF).
 -- 

With video-size set to 0, clicking on camera button,
zooming to max, ie 352x288. Quite bad pixelation.
Now setting video-size to 1. Size doubles, so zooming 
back to 352x288. Almost no visible pixelation. Clearly
CIF.
Calling [EMAIL PROTECTED] Local shrinks to half. So zooming
in to get 352x288. The same bad pixelation as at the
beginning. After remote appears, it is as bad as local.
Clearly QCIF.

Maybe I\'m doing something wrong but I am pretty sure that 
it is QCIF that is being sent... 



__
Mobilné telefóny v slovenskej premiére a najaktuálnejšie informácie - 
http://mobil.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CIF over h261 on Ekiga 2.0

2007-11-02 Thread Palo S .

 
 There is no easy fix. However, I think I remember there was a GConf key
 in the Ekiga arborescence to force video to large. The key is
 video_size, and if I remember correctly, it should be set to \1\.
 -- 

There is no video_size key for ekiga in gconf. And adding video_size 
of integer type to video section and setting it to 1 does not change 
anything. 


__
http://diplomovka.sme.sk - Odme#328;ujeme vaše diplomové práce.


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Fwd: How do I video chat with Windows users?

2007-07-24 Thread Palo S .

I tried Ekiga on Linux with Ekiga on Windows, video did not work at all, sound 
worked usually for several minutes only - suddenly, it began to give you only 
loud \knocking\ at both ends... I did not have access to the Windows end 
(probably responsible for the problem) so I could not see the -d output from 
Windows machine...





__
Mozaika storočia denníka SME - http://mozaika.sme.sk


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] Fwd: Re: Re: Fwd: How do I video chat with Windows users?

2007-07-24 Thread Palo S .


 Did you try version 2.0.10 for windows?
 http://ekiga.net/misc/ekiga-setup-2.0.10-BETA.exe

No, it was 2.0.9 beta for Windows - I will tell my friend to install 2.0.10 
on his Windows machine and get back here soon!


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] GConf error under Windows version

2007-07-16 Thread Palo S .

Hi all,

I get GConf key error of invalid value of gconf_test_age
when starting the Windows version of Ekiga. On the webpage
on Ekiga troubleshooting I found that I should delete the file
C:\\Documents and Settings\\YOUR LOGIN\\Applications Data\\ekiga.conf
to fix this, however, there is no such file. Reinstallation
of GTK and Ekiga does not help. I tried to search for a file that
could store some Ekiga or Gconf configuration which is not
removed when Ekiga and GTK are uninstalled, however, I could
not find anything...






__
http://zabava.sme.sk/ - Stránka čo usmeje ti tvár


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Webcam Doesn\'t Scale

2007-05-26 Thread Palo S .

I have the same problem of image not scaling with
Labtec Pro. It uses gspca too, however, the driver
reports \minw 176 minh 144\ (ie it knows that QCIF
is not supported so the problem is not here in this
case). This is with 2.0.9 version of Ekiga on 
2.6.20-1.2933.fc6 kernel.




__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Webcam Doesn\'t Scale

2007-05-26 Thread Palo S .

If I understand it correctly, Damien and you say
that the problem is caused by the driver advertising 
it supports QCIF when it does not. But in my case the 
driver knows that QCIF is not supported - so I assume
that the problem lies somewhere else? Or do you mean
that the driver may still advertise it supports QCIF 
to Ekiga even though it internally knows that it does 
not? (Is there a simple way to find this out?)



- Originálna Správa -
Od: Julien Puydt  
Komu: Ekiga mailing list  
Poslaná: 26.05.2007 13:02 
Predmet: Re: [Ekiga-list] Webcam Doesn\\\'t Scale

 Palo S. a écrit :
  I have the same problem of image not scaling with
  Labtec Pro. It uses gspca too, however, the driver
  reports \\\minw 176 minh 144\\\ (ie it knows that QCIF
  is not supported so the problem is not here in this
  case). This is with 2.0.9 version of Ekiga on
   2.6.20-1.2933.fc6 kernel.
 
 Then obviously the answer to the problem is the same... or did you ask
  something different ?
 
 Snark on #ekiga
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 


__
Najpopulárnejší blog na Slovensku - http://blog.sme.sk/


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] video regression in SVN?

2007-05-20 Thread Palo S .


 Recent changes were done in the video code in the SVN, and since then my
 camera does not work anymore in small size either.

My camera does not work in any size (neither normal nor large)



__
http://sport.sme.sk - Najkomplexnejšie informácie zo športu


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list