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