OPAL - Problems with Gatekeeper

There are two issues with OPAL trying to register at a gatekeeper:
This appeared both using simpleopal and my own app (XMeeting on MacOSX).

Eventually, these bugs are already known, but I'll report them anyway:

When being behind a NAT, the OPAL library hangs, waiting for a response 
from the gatekeeper. I do have to investigate this problem more 
in-depth in order to find out more. All I can tell is that I have 
absolutely no problems registering at the gatekeeper using 
ohphone/OpenH323.
I have seen that the implementation of both ip address translation and 
much of the gatekeeper code differ in openh323 / OPAL. I guess the 
openh323 implementation is the newer one and OPAL uses a new approach 
which still has some bugs. Is this correct?

The second problem occurs after a succesful gatekeeper registration.
About 1 - 2 minutes after the succesful registration, the registration 
disappears from the gatekeeper. I suspect that the OPAL library fails 
to answer the keep-alive requests, which causes the gatekeeper to 
remove the registration.

When looking at the PTRACE log from simpleopal, I find the following 
line:

0:18.690    Transactor:552cf0    h323trans.cxx(196)    H225RAS Write 
PDU failed (9): Bad file descriptor

Is the assumption correct that OPAL fails sending an answer due to an 
incorrect file descriptor?

Thanks

Hannes

------------------------------------------------------------------------
Check the FAQ before asking! - http://www.openh323.org/~openh323/fom.cgi
The OpenH323 Project mailing list, using Mailman. To unsubscribe or
change your subscription options, goto
http://www.openh323.org/mailman/listinfo/openh323
Maintained by Quicknet Technologies, Inc - http://www.quicknet.net
------------------------------------------------------------------------