Re: [Ekiga-devel-list] Incoming calls not detected [latest]

2007-01-31 Thread thomas schorpp
Craig Southeren wrote:
 On Wed, 31 Jan 2007 11:49:25 +0100
 thomas schorpp [EMAIL PROTECTED] wrote:
 
 ..deleted
 
 
11:42:01 Remote user rejected the call


- d4 log attached-
 
 
 Thanks for this. I can now be fairly sure the problem is related to changes
 in the way that OnIncomingConnection is now handled.
 
 I've been trying to make the code backwards compaibnle, but it looks
 like that is not going to work. Once we have Ekiga working again, I will
 be modify OPAL to ensure that code will fail to compile, rather than
 breaking silently. 
 
 Looking at Ekiga, I can see one change that will need to be made.
 
 in manager.cpp, near line 909, the following code:
 
  case 0:
 res = OpalManager::OnIncomingConnection (connection);
 break;
 
 
 should be changed to
 
  case 0:
 res = OpalManager::OnIncomingConnection (connection, 0, NULL);
 break;
 
 if you can try this, let me know if it makes a difference
 
   Craig

well, at least no more immediate call rejects, but I still cant take the call:

12:27:09 Started Ekiga 2.1.0 for user schorpp
12:27:20 Set STUN server to stun.sipgate.net (Port Restricted NAT)
12:28:29 Remote user has stopped calling
12:29:31 Remote user has stopped calling
12:29:51 Calling sip:[EMAIL PROTECTED]
12:30:03 Opened VIA 8237 for recording with plugin ALSA
12:30:03 Opened codec Speex for transmission
12:30:03 Opened VIA 8237 for playing with plugin ALSA
12:30:03 Opened codec Speex for reception
12:30:03 Opening video device StaticPicture with plugin Picture
12:30:03 Successfully opened video device StaticPicture, channel 0
12:30:03 Opened codec h261 for transmission
12:30:03 Opened codec h261 for reception
12:30:03 Connected with schorpp using 
12:30:15 Closed codec Speex which was opened for transmission
12:30:15 Closed codec Speex which was opened for reception
12:30:15 Closed codec h261 which was opened for transmission
12:30:16 Closed codec h261 which was opened for reception
12:30:16 Remote user cleared the call
12:31:12 Remote user has stopped calling
12:35:25 Remote user has stopped calling


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


[Ekiga-devel-list] Fw: Crash on Ekiga Startup [latest]

2007-01-31 Thread Jan Schampera

(forgot to CC the mailinglist)

Start of forwarded message:

Date: Wed, 31 Jan 2007 22:40:40 +0100
From: Jan Schampera [EMAIL PROTECTED]
To: Craig Southeren [EMAIL PROTECTED]
Subject: Re: [Ekiga-devel-list] Crash on Ekiga Startup [latest]


On Wed, 31 Jan 2007 17:23:53 +1100
Craig Southeren [EMAIL PROTECTED] wrote:

   Is there any chance of running a debug version and seeing if you
   can get somethng more useful?
  
  Tonight after work.
 
 Thanks!

Checked out versions from 15. January also crash, so I guess the
problem is home-made somehow, and not to be seen critical. Sorry for
the wind (it appeared just after updating, the libs that were installed
before worked).

J.


-- 
I know life sometimes can get tough! and I know life sometimes can be a
drag! But people, we have been given a gift, we have been given a road
And that roads name is... rock and roll!
KISS in God gave Rock'n'Roll to you


-- 
Dr. Postel passes away, the Internet survives. There can be no greater
tribute. As long as the Internet stands, it will remain a monument to
his life's work.
- Harold Feld, General Counsel, Domain Name Rights Coalition
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] Incoming calls not detected [latest]

2007-01-31 Thread Craig Southeren
On Wed, 31 Jan 2007 10:33:46 -0800 (PST)
Andre Kirchner [EMAIL PROTECTED] wrote:

 I'm also running into this problem.
 I took a quick look in the code, and think the following is happening
 
 1. GMSIPEndPoint::OnIncomingConnection calls 
 OpalManager::OnIncomingConnection (OpalConnection, unsigned, 
 OpalConnection::StringOptions)
 
 2. Class GMManager extends OpalManager, and method OnIncomingConnection 
 (OpalConnection, int, PString) should overload method 
 OpalManager::OnIncomingConnection (OpalConnection, unsigned, 
 OpalConnection::StringOptions), and be called
 
 3. Method GMManager::OnIncomingConnection calls 
 gm_main_window_incoming_call_dialog_show, and then calls 
 OpalManager::OnIncomingConnection (OpalConnection) that calls 
 OpalManager::OnIncomingConnection (OpalConnection, unsigned), that calls 
 OpalManager::OnIncomingConnection (OpalConnection, unsigned, 
 OpalConnection::StringOptions)
 
 The problem should be that signatures of methods 
 GMManager::OnIncomingConnection (OpalConnection, int, PString) and 
 OpalManager::OnIncomingConnection (OpalConnection, unsigned, 
 OpalConnection::StringOptions) are different.
 I'll take a better look in the code when I have more time.
 
 Andre

I posted a hopeful fix for this problem yesterday.

Here is what I posted:


Looking at Ekiga, I can see one change that will need to be made.

in manager.cpp, near line 909, the following code:

 case 0:
res = OpalManager::OnIncomingConnection (connection);
break;


should be changed to

 case 0:
res = OpalManager::OnIncomingConnection (connection, 0, NULL);
break;

if you can try this, let me know if it makes a difference

   Craig


---
 Craig Southeren  Post Increment – VoIP Consulting and Software
 [EMAIL PROTECTED]   www.postincrement.com.au

 Phone:  +61 243654666  ICQ: #86852844
 Fax:+61 243656905  MSN: [EMAIL PROTECTED]
 Mobile: +61 417231046  Jabber: [EMAIL PROTECTED]

 It takes a man to suffer ignorance and smile.
  Be yourself, no matter what they say.   Sting


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


Re: [Ekiga-list] ekiga-list Digest, Vol 6, Issue 48

2007-01-31 Thread gabbro ...



From: [EMAIL PROTECTED]
Reply-To: ekiga-list@gnome.org
To: ekiga-list@gnome.org
Subject: ekiga-list Digest, Vol 6, Issue 48
Date: Tue, 30 Jan 2007 12:00:27 -0500

Send ekiga-list mailing list submissions to
   ekiga-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
   http://mail.gnome.org/mailman/listinfo/ekiga-list
or, via email, send a message with subject or body 'help' to
   [EMAIL PROTECTED]

You can reach the person managing the list at
   [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than Re: Contents of ekiga-list digest...


Today's Topics:

1. Re: Ekiga too slow after zoom in? (yannick)
2. Re: Ekiga too slow after zoom in? (Jan Kasprzak)


--

Message: 1
Date: Mon, 29 Jan 2007 22:46:05 +0100
From: yannick [EMAIL PROTECTED]
Subject: Re: [Ekiga-list] Ekiga too slow after zoom in?
To: Ekiga mailing list ekiga-list@gnome.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=utf-8

On lun, 2007-01-29 at 14:24 +0100, Damien Sandras wrote:
  Hi,
 
  Le lundi 29 janvier 2007 ? 14:22 +0100, Jan Kasprzak a ?crit :
 Hello,
  
   does ekiga use Xvideo for displaying the video stream? I use ekiga 
against
   another ekiga, and when I zoom in (View - Zoom in) during the call,
   the CPU time usage becomes 100%, resulting in choppy sound and other
   problems.
  
 Tested on AMD Athlon64 FX-51 (2.2 GHz) and Athlon 3000+ (2166 MHz),
   where mplayer has not a problem displaying much larger video (640x480,
   for example).
  
 
 
  That sounds a bit much.

I've an Athlon 64 3000+ (running Ekiga in 64 bits). Ekiga 2.0.3 takes
about 20% of the CPU at 1GHz when I zoom in.

I've stressed it using the CVS version with large video and zoom in; it
takes about 90% of the CPU at 1.8 GHz

My gfx card is : GeForce 6200 using its own RAM.

Regards,
Yannick

 
  Howeve,r I have a XV patch waiting in my queue for the next release of
  Ekiga...
 
 Thanks,
  
   -Yenya
  
  --
   _  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
--
Me joindre en t?l?phonie IP / vid?oconf?rence ?
sip:[EMAIL PROTECTED]



--

Message: 2
Date: Mon, 29 Jan 2007 23:06:14 +0100
From: Jan Kasprzak [EMAIL PROTECTED]
Subject: Re: [Ekiga-list] Ekiga too slow after zoom in?
To: Ekiga mailing list ekiga-list@gnome.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1

yannick wrote:
:  Le lundi 29 janvier 2007 ? 14:22 +0100, Jan Kasprzak a ?crit :
:   does ekiga use Xvideo for displaying the video stream? I use ekiga 
against
:   another ekiga, and when I zoom in (View - Zoom in) during the call,
:   the CPU time usage becomes 100%, resulting in choppy sound and other
:   problems.
:  
:Tested on AMD Athlon64 FX-51 (2.2 GHz) and Athlon 3000+ (2166 MHz),
:   where mplayer has not a problem displaying much larger video 
(640x480,
:   for example).
: 
:  That sounds a bit much.
:
: I've an Athlon 64 3000+ (running Ekiga in 64 bits). Ekiga 2.0.3 takes
: about 20% of the CPU at 1GHz when I zoom in.
:
: I've stressed it using the CVS version with large video and zoom in; it
: takes about 90% of the CPU at 1.8 GHz
:
: My gfx card is : GeForce 6200 using its own RAM.

   My display is ATI RV200 (Radeon 7500) on Athlon64,
ATI RV280 (Radeon 9200 SE) on Athlon 3000+.

   I tried to call [EMAIL PROTECTED], and it seems the problem was worse
on the Athlon64 side - on the Athlon 3000+ the normal CPU usage is around 
40%,
while after zoom in it is around 85% (iLBC/H261 codecs), and just 
sometimes
it raises to 100%. Also the CPU usage remains high even when I minimize the
ekiga window.

-Yenya

--
| Jan Yenya Kasprzak  kas at {fi.muni.cz - work | yenya.net - private} 
|
| GPG: ID 1024/D3498839  Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E 
|
| http://www.fi.muni.cz/~kas/Journal: http://www.fi.muni.cz/~kas/blog/ 
|
  I will never go to meetings again because I think  face to face meetings 

  are the biggest waste of time you can ever have.--Linus Torvalds 



--

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

End of ekiga-list Digest, Vol 6, Issue 48
*
i'd like don't receive anymore your mail  how can I
stop it?
please let me now
greettings

_
Aggiungi i tuoi nuovi contatti di Hotmail anche in Messenger.Con un click! 

Re: [Ekiga-list] ekiga-list Digest, Vol 6, Issue 48

2007-01-31 Thread Anthony Messina
On Wed, 2007-01-31 at 16:19 +0100, gabbro ... wrote:
 To subscribe or unsubscribe via the World Wide Web, visit
  http://mail.gnome.org/mailman/listinfo/ekiga-list
 or, via email, send a message with subject or body 'help' to
  [EMAIL PROTECTED]

you follow the above instructions, quoted from the email you sent.

or simply send an email to [EMAIL PROTECTED] with
unsubscribe in the subject.

-- 
Anthony -  http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E


signature.asc
Description: This is a digitally signed message part
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga 2.04 and ALSA

2007-01-31 Thread Rene Bartsch

 Since I have upgraded to Ekiga 2.04, I can no longer use the default
 device for input or output. I have to use my sound card directly. I was
 wondering if anyone else was experiencing this problem?


I had that problem with Ekiga-2.0.3. With 2.0.4 it's gone :-)

Maybe you have to edit you asound.conf ...

Renne

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


Re: [Ekiga-list] Ekiga 2.04 and ALSA

2007-01-31 Thread Derek Smithies
Hi,
 sound on linux continues to be a problem.

In some of my darker momements, I have mispronounced ALSA as
ulcer. 

So where is real problem?
The alsa plugins in pwlib follow the alsa examples, and should
be correct. Then a bit of reading finds that between alsa
1.0.10 and 1.0.11   (or was it 1.0.11 and 1.0.12?) that the alsa
internals were changed to add an extra dmix operator in the 
system asound.conf  and I just don't get it.

Do we decide that the direction of alsa is not right for this project
and work on a openal based plugin. Will that be more reliable ?

=
On Wed, 31 Jan 2007, Rene Bartsch wrote:
 Maybe you have to edit you asound.conf ...
An activity which is technically challenging, and not for the faint 
hearted. Further,  upgrades to your box will have an unknown outcome.

Derek.
-- 
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: [EMAIL PROTECTED]
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ?

2007-01-31 Thread Jan Schampera
On Wed, 31 Jan 2007 22:12:05 +0100
Kováts Zoltán [EMAIL PROTECTED] wrote:

 Hi Sandras,
 
 So, the Ekiga-message after Ekiga calling is:
 20:18:57 A Ekigat (2.0.3 verzió) elindította kz felhasználó
 20:18:58 STUN kiszolgáló beállítása a következőre: stun.ekiga.net
 (Tölcsér NAT)
 20:18:59 Regisztrálva a következőre: ekiga.net
 20:18:59 A regisztráció meghiúsult: A regisztráció meghiúsult
 20:18:59 kzfrombud regisztrációja meghiúsult ezen: Kovats Zoltan
 (The registration of kzfrombud is miscarried on:Kovats Zoltan)

Just as sidenote, you can force english output by setting LC_ALL to C:
shell$ LC_ALL=C ekiga
or
shell$ export LC_ALL=C; ekiga

J.

-- 
dreaming in digital
living in realtime
thinking in binary
talking in IP

WELCOME TO OUR WORLD

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

[Ekiga-list] Ekiga not working under NAT and using STUN

2007-01-31 Thread Andrés Gómez García
Hi!

I suppose this question has been made several times but I've read
everything about this issue (FAQ and mailing lists) and, even knowing it
should work with my configuration, I'm not being successful on this.

I will explain the situation.

- I've two computers in my home lan network. IP's 192.168.1.101 and
192.168.1.102.
- These computers are connected through a Linksys WiFi router among them
and to the Internet.
- The linksys router is connected to the Internet with a public dynamic
IP.
- One of my computers runs Ubuntu Edgy with Ekiga 2.0.3 and
Ekiga-snapshot (2.1.0)
- The other computer runs Debian SID with Ekiga 2.0.3 and Windows with
Ekiga (2.1.0) and XTen Lite 3.0
- When running the NAT test with Ekiga (Ubuntu, Debian and Windows) it
says I've Port Restricted NAT. With XTen it says Cone NAT. Every of
them are configured to use STUN: stun.ekiga.net.
- I'm successfull calling from every computer to [EMAIL PROTECTED]
- I'm not able to call to another ekiga.net user who is outside my
network nor another ekiga.net user outside my network is able to call
me. It rings for a while but the call signal doesn't reach the other
end.
- I'm able to register two ekiga.net users in my two computers at the
same time with Ekiga (Linux, Win32) and XTen but I'm not able to
stablish a call between my two computers through the ekiga users. The
only way it works is calling from Ekiga to XTen. It doesn't work calling
Ekiga to Ekiga (nor Linux, neither Windows) nor XTen to Ekiga.
- I'm able to call Ekiga to Ekiga or Ekiga/XTen to XTen/Ekiga through my
private IP adressess; sip:192.168.1.101 to sip:192.168.1.102

I need some tip/help. Where is the problem?

Thanks in advance.
-- 

Ciao.
 
=
Andrés Gómez García
tanty en confluencia punto net 
Usuario Linux: 276916
Estación Linux: 159599
JabberID: [EMAIL PROTECTED]

=
Puedes encontrar mi clave pública en la siguiente dirección:
http://pgp.rediris.es:11371/pks/lookup?search=0x3FEA1034op=index
Mi correo va firmado digitalmente con GnuPG. Puedes encontrar
información al respecto en:
http://www.gnupg.org


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list