[GnomeMeeting-list] GnomeMeeting and NetMeeting

["James K. Wiggs" <wiggs wiggs org>]

 Folks,

   I'm trying to set up a Linux box and an NT 4.0 box to connect
over the net; each one is behind an LRP firewall box.  Both LRP
boxes have been configured to portforward ports 1503, 1720, and
1731 to the appropriate machines.  I've installed the appropriate
masquerading module on each machine ip_masq_h323.  Running nmap
shows that the appropriate ports are open.  I've configured a box
behind the same firewall as the NT box to act as an LDAP server,
with the netmeeting tweaks installed, as well.  The Linux box
here can connect to the LDAP server and register itself.  All
seems well, except that we can't actually connect.  If I try to
make a connection from GnomeMeeting, it instantly disconnects.
If he makes a call to me from NetMeeting, I get notified of the
incoming call, but it doesn't auto-answer (even though that has
been enabled under settings).  If I click on the little "connect"
button to force a connection, it acts as though the call has
been connected, the timer starts counting up, and 30 seconds
later I get an "abnormal disconnect" message.  During the entire
process, there is *never* *any* indication on his end that any
sort of connection has been made.  I've got about 700 lines of
debugging output, and I'll try to sort through what looks to be
of any use.  Oh, yes: we have installed the GSM codec under his
NetMeeting directory.

Here's what looks relevant from the debugging information:

  9:15.092        H323 Listener:8192c40 H323TCP Started connection to
24.164.5.128:61102 (if=192.168.100.10:1720)
  9:15.092        H323 Listener:8192c40 TCP     Waiting on socket accept
on ip$*:1720
  9:15.093          H225 Answer:81c1f20 H225    Started incoming call
thread
  9:15.093          H225 Answer:81c1f20 H225    Awaiting first PDU
  9:15.244          H225 Answer:81c1f20 H225    Received raw data:

[ Raw Data Removed ]

  9:15.275          H225 Answer:81c1f20 H225    Received PDU:

[ More Raw Data Removed ]

  9:15.327          H225 Answer:81c1f20 H225    Incoming call, first PDU:
callReference=27735
  9:15.328          H225 Answer:81c1f20 H323    Added capability:
GSM-06.10{sw}
<1>
  9:15.328          H225 Answer:81c1f20 H323    Added capability:
MS-GSM{sw} <2>  9:15.329          H225 Answer:81c1f20 H323    Added
capability: H.261-QCIF <3>  9:15.329          H225 Answer:81c1f20 H323
Added capability: H.261-CIF <4>
  9:15.330          H225 Answer:81c1f20 H323    FindCapability: 1
  9:15.330          H225 Answer:81c1f20 H323    Found capability:
GSM-06.10{sw}
<1>
  9:15.330          H225 Answer:81c1f20 H323    FindCapability: 2
  9:15.331          H225 Answer:81c1f20 H323    Found capability:
MS-GSM{sw} <2>  9:15.331          H225 Answer:81c1f20 H323
FindCapability: 3
  9:15.332          H225 Answer:81c1f20 H323    Found capability:
H.261-QCIF <3>  9:15.332          H225 Answer:81c1f20 H323
FindCapability: 4 
  9:15.332          H225 Answer:81c1f20 H323    Found capability:
H.261-CIF <4>
  9:15.333          H225 Answer:81c1f20 RFC2833 Handler created
  9:15.334          H225 Answer:81c1f20 H323    Created new connection:
ip$24.164.5.128:61102/27735
  9:15.334          H225 Answer:81c1f20 H225    Handling PDU: Setup
callRef=27735
  9:15.335          H225 Answer:81c1f20 H225    Set remote application
name: "Microsoft NetMeeting    3.0     181:0:21324"
  9:15.336          H225 Answer:81c1f20 H225    Sending call proceeding
PDU
  9:15.342          H225 Answer:81c1f20 H225    Sending PDU:

[ More Raw Data Removed ]

  9:15.388          H225 Answer:81c1f20 H225    Incoming call accepted
  9:15.906          H225 Answer:81c1f20 H323    Answering call:
AnswerCallNow
  9:15.907          H225 Answer:81c1f20 H225    TCP Listen for H245 on
192.168.100.10:2607
  9:15.908                 H245:81df160 H245    Started thread
  9:15.908                 H245:81df160 H245    TCP Accept wait
  9:15.910          H225 Answer:81c1f20 H225    Sending PDU:

[ More Raw Data Removed ]

  9:15.952          H225 Answer:81c1f20 H323
InternalEstablishedConnectionCheck:
connectionState=HasExecutedSignalConnect fastStartState=FastStartDisabled
  9:15.953          H225 Answer:81c1f20 H323
InternalEstablishedConnectionCheck:
connectionState=HasExecutedSignalConnect fastStartState=FastStartDisabled
  9:15.954          H225 Answer:81c1f20 H225    Reading PDUs:
callRef=27735
  9:25.747                 gnomemeeting H323    Answering call:
AnswerCallNow
  9:25.747                 gnomemeeting H323
InternalEstablishedConnectionCheck:
connectionState=HasExecutedSignalConnect fastStartState=FastStartDisabled
  9:45.905                 H245:81df160 H225    Accept for H245 failed:
Interrupted system call
  9:45.905                 H245:81df160 H323    Clearing connection
ip$24.164.5.128:61102/27735 reason=EndedByTransportFail
  9:45.906                 H245:81df160 H323    Call end reason for
ip$24.164.5.128:61102/27735 set to EndedByTransportFail
  9:45.906                 H323 Cleaner H323    Cleaning up connections
  9:45.907                 H323 Cleaner H323    Connection
ip$24.164.5.128:61102/27735 closing:
connectionState=HasExecutedSignalConnect
  9:45.907                 H323 Cleaner H225    Sending release complete
PDU: callRef=27735
  9:45.912                 H323 Cleaner H225    Sending PDU:

[ More Stuff Removed ]

  9:45.928                 H323 Cleaner H323    H323Transport::Close
  9:46.094          H225 Answer:81c1f20 H225    Read error (9): Bad file
descriptor
  9:46.094          H225 Answer:81c1f20 H323    Clearing connection
ip$24.164.5.128:61102/27735 reason=EndedByTransportFail
  9:46.095          H225 Answer:81c1f20 H323    H323Transport::Close
  9:46.095          H225 Answer:81c1f20 H225    Signal channel closed.
  9:46.246                 H323 Cleaner H323
H323Transport::CleanUpOnTermination for H225 Answer:81c1f20
  9:46.247                 H323 Cleaner H323    H323Transport::Close
  9:46.248                 H323 Cleaner H323
H323Transport::CleanUpOnTermination for H245:81df160
  9:46.248                 H323 Cleaner H323    Connection
ip$24.164.5.128:61102/27735 terminated.

And that seems to be the end of the relevant stuff.  It looks like it
is failing due to use of H245, but I have H245 disabled in the Settings
window; why should it even be trying.  The FAQ says it isn't supported
currently for connections through firewalls, as I recall, which is why
I switched it off.  Can anyone shed some light on what's going on here?
I've been through all the FAQs and searched the mailing list archives,
and it appears that there must be plenty of people successfully using
this sort of setup, but I can't get it to work.

best,
Jim Wiggs


James Wiggs
Email: wiggs wiggs net
ICBM: 97 30 18 W, 42 52 27 N