[GnomeMeeting-devel-list] SIP "Registration failed after sucessful registration with multiple network interfaces" - bug
- From: Jan Schiefer <cheaterjs gmx de>
- To: gnomemeeting-devel-list gnome org
- Subject: [GnomeMeeting-devel-list] SIP "Registration failed after sucessful registration with multiple network interfaces" - bug
- Date: Wed, 13 Apr 2005 17:59:37 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I figured out how this works.
You create a SIPTransaction for each Interface except lo ( eth0, ppp0 ...) .
The one on ppp0 registers sucessfully to the SIP server and stops the
retryTimer in SIPTransaction::SetTerminated(States newState).
But somehow the SIPTransaction for eth0 think's it is registering too. (
What is just plain wrong. ) Here the timer isn't stopped. After a short
time we get a "Terminated_TransportError for 1 REGISTER" here. BANG!
Gnomemeeting thinks registration has failed.
I just hacked opal/src/opal/transports.cxx:
BOOL OpalTransportUDP::Connect()
{
...
for (i = 0; i < interfaces.GetSize(); i++) {
PIPSocket::Address interfaceAddress = interfaces[i].GetAddress();
if (interfaceAddress == 0 || interfaceAddress == PIPSocket::Address())
continue;
to
BOOL OpalTransportUDP::Connect()
{
...
for (i = 0; i < interfaces.GetSize(); i++) {
PIPSocket::Address interfaceAddress = interfaces[i].GetAddress();
if (interfaceAddress == 0 || interfaceAddress ==
PIPSocket::Address() || interfaceAddress ==
PIPSocket::Address("192.168.0.1"))
continue;
And the error vanished.
Unfortunately I didn't find the exact source of the problem.
Greetings,
Jan Schiefer!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCXUHpzC00UKXFdVcRAtFnAKC4i2fzR2pkOwsoc8NzggqiUWMX+gCgjB86
08fCiY10csib59OnBNyK8BE=
=0IuO
-----END PGP SIGNATURE-----
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]