Re: [GnomeMeeting-list] Ekiga && Media patch thread not terminated
- From: Matthias Apitz <guru Sisis de>
- To: GnomeMeeting mailing list <gnomemeeting-list gnome org>
- Subject: Re: [GnomeMeeting-list] Ekiga && Media patch thread not terminated
- Date: Fri, 23 Jun 2006 16:51:53 +0200
El día Thursday, June 22, 2006 a las 04:20:29PM +0200, Damien Sandras escribió:
> I don't understand your network, neither from where the debug output is
> coming.
Hi Damien,
We run an ipfilter based firewall which hides the LAN behind one
external IP addr with NAT. I've opened for my two laptops all
outgoing ports TCP and UDP > 1024 and I have no other firewall on
the laptops active. For incoming IP there are no special NAT redirect
rules, ie. only an outgoing UDP or TCP let come in a pkg for the
same connection.
> However, I have two remarks :
> 1) OSS is being used. There was a bug until Ekiga 2.0.2, so make sure it
> is Ekiga 2.0.2
> 2) You do not receive anything, you only send (see Final statistics),
> firewall ?
...
I spend a lot of time testing both installations of Ekiga 2.0.2 in
the two laptops.... Both are configured the same way (NAT Traversal
Method: STUN, server: stun.ekiga.net, and for each of them I've
registered a separate login in 'ekiga.net').
The results are as following.
1. On both systems the registering to the server 'ekiga.net' is not
very stable, sometimes it registers on first shoot; sometimes you
can try it for half an hour in the tab of the accounts to get it
registered; is there some load problem?
2. Calling up <500 ekiga net> gives a lot of times 'abnormal call
termination' and in tcpdump you see some CANCEL:
16:32:33.142224 IP 213.186.62.145.5060 > 193.31.10.34.5073: SIP
0x0000: 4500 028e 96ac 4000 3511 cd25 d5ba 3e91 E 5 % >.
0x0010: c11f 0a22 13c4 13d1 027a 3d1a 5349 502f ...".....z=.SIP/
0x0020: 322e 3020 3438 3020 4f66 666c 696e 650d 2.0.480.Offline.
0x0030: 0a43 5365 713a 2031 2043 414e 4345 4c0d .CSeq:.1.CANCEL.
0x0040: 0a56 6961 3a20 5349 502f 322e 302f 5544 .Via:.SIP/2.0/UD
sometimes the call to <500 ekiga net> is successful;
3. when it is successful to <500 ekiga net> (the echo-room) I was able
with the FreeBSD 6.1-RELEASE client to hear the greeting message about
the echo-test and in this case traffic goes really in both
directions:
16:25:22.353350 IP 193.31.10.35.5068 > 213.186.62.145.5060: SIP, length: 994
16:25:22.382952 IP 213.186.62.145.5060 > 193.31.10.35.5068: SIP, length: 717
16:25:22.387092 IP 193.31.10.35.5068 > 213.186.62.145.5060: SIP, length: 456
16:25:22.515066 IP 193.31.10.35.5068 > 213.186.62.145.5060: SIP, length: 1199
16:25:22.551039 IP 213.186.62.145.5060 > 193.31.10.35.5068: SIP, length: 589
16:25:22.554913 IP 213.186.62.145.5060 > 193.31.10.35.5068: SIP, length: 881
16:25:22.562555 IP 193.31.10.35.5068 > 213.186.62.145.5060: SIP, length: 791
16:25:25.081279 IP 193.31.10.35.5000 > 213.186.62.145.15180: UDP, length 172
16:25:25.084729 IP 213.186.62.145.15180 > 193.31.10.35.5000: UDP, length 172
16:25:25.102974 IP 213.186.62.145.15180 > 193.31.10.35.5000: UDP, length 172
16:25:25.107273 IP 193.31.10.35.5000 > 213.186.62.145.15180: UDP, length 172
16:25:25.120021 IP 193.31.10.35.5000 > 213.186.62.145.15180: UDP, length 172
16:25:25.124720 IP 213.186.62.145.15180 > 193.31.10.35.5000: UDP, length 172
16:25:25.130268 IP 193.31.10.35.5000 > 213.186.62.145.15180: UDP, length 172
16:25:25.141841 IP 213.186.62.145.15180 > 193.31.10.35.5000: UDP, length 172
4. with the FreeBSD 6.0-RELEASE client in a successfull call to
<500 ekiga net> at the beginning I only see outbound traffic after
the SIP exchange; und it does not play the greeting message:
17:09:03.846499 IP 213.186.62.145.5060 > 193.31.10.34.5065: SIP, length: 592
17:09:03.850497 IP 213.186.62.145.5060 > 193.31.10.34.5065: SIP, length: 885
17:09:03.862065 IP 193.31.10.34.5065 > 213.186.62.145.5060: SIP, length: 795
17:09:04.650027 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1024
17:09:04.650526 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1000
17:09:04.651025 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 971
17:09:04.653150 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1007
17:09:04.653650 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1019
17:09:04.653899 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 497
17:09:07.540796 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1024
17:09:07.542170 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1000
17:09:07.548294 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 971
17:09:07.548919 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1007
17:09:07.549419 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 1019
17:09:07.549794 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 497
17:09:09.621361 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:11.550206 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:13.529043 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:15.554244 IP 193.31.10.34.5031 > 213.186.62.145.19821: UDP, length 72
17:09:15.554494 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:17.522707 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:19.553533 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:21.532618 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:23.537199 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:25.539905 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:25.560062 IP 213.186.62.145.19820 > 193.31.10.34.5030: UDP, length 30
17:09:27.526864 IP 193.31.10.34.5030 > 213.186.62.145.19820: UDP, length 30
17:09:27.546996 IP 213.186.62.145.19820 > 193.31.10.34.5030: UDP, length 30
17:09:29.633174 IP 193.31.10.34.5031 > 213.186.62.145.19821: UDP, length 96
5. with the FreeBSD 6.0-RELEASE client must be something completely
broken, I think; on launching it with -d3 it says 6 times at the
beginning:
(ekiga:13943): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT
(object)' failed
maybe the cause for the problem of the Subject:?
Thx
matthias
--
Matthias Apitz
Manager Technical Support - OCLC PICA GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <m apitz oclcpica org> - w http://www.oclcpica.org/ http://guru.UnixLand.de/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]