Re: [GnomeMeeting-list] About the registration to an ILS directory

[Paul <paul666 mailandnews com>]

On Sun, 2 Dec 2001, Katsumi Saito wrote:
Hi,

> In the following composition, there is a problem.
> 
>        NAT
> PC ------------ ADSL modem ------- InterNet
> Private         Global
> IP Address      IP Address
> 
> Since it has registered with free DNS, by the host name registered, about me, 
> it is the following scripts and it has been registered into ILS.
> 
> --
> nmaddentry -h ils.servername -c Comment -l Location -g Katsumi -s Saito -v 
> katsumi jo1upk ymt prug or jp xxxxx.dnsalias.com
> ---
> 
> It is convenient if the following options are in GnomeMeeting.
> 
> o The IP address of self-PC is registered. (The present function)
> o It registers using the specified host name.

There are currently a few issues with ILS registration that make
the process somewhat complicated. First, the server only knows one
thing about about the client, and that is the IP address of the
client as supplied by the client in decimal (sipaddress). It
obviously can also know the IP address that is used to connect
to the server, but I don't think a typical ILS uses that. If you
register to argo.dyndns.org you will find that it ignores the
IP address presented by the client and substitutes the IP
address of the peer.

You also cannot register a hostname, nor indicate to ILS that
your client is behind a NAT gateway and thus needs to be addressed
specially.

Lastly, there are so many possibilities of things that you might
want to do, that getting gnomemeeting to support them all would
be a never ending job.

To solve some of these problems, I've written a replacement
for some of the ILS client functionality that I've proposed for
gnomemeeting. With my proposal, GM will supply various pieces of
information to the ILS registration library, however the exact
functionality and any additional data will be controlled by
a file in XML.

Here's an example to illustrate:

<?xml version="1.0"?>
<!-- Configuration file to register with a netmeeting ILS server -->
<!-- Replicates activity of a netmeeting client -->
<!-- Any entities here will override runtime values -->
<!DOCTYPE ils SYSTEM "ils.dtd" [
<!-- A netmeeting client will only search for ms-netmeeting sappids -->
<!ENTITY sappid "ms-netmeeting"> <!-- Override gnomemeeting's sappid -->
]>
<ils host="&host;" port="&port;" method="SIMPLE">
<!-- No need to create parent objects -->
<!-- Add the record itself, after deleting it -->
 <delete ignore="noobject">
  <dn>c=&country;,o=&org;,cn=&email;,objectclass=&class;</dn>
 </delete>
 <add>
  <dn>c=&country;,o=&org;,cn=&email;,objectclass=&class;</dn>
  <cn>&email;</cn>
  <sipaddress>&decip;</sipaddress>
  <givenname>&givenname;</givenname>
  <surname>&surname;</surname>
  <rfc822mailbox>&email;</rfc822mailbox>
  <location>&location;</location>
  <comment>&comment;</comment>
  <ilsa32833566>&audio;</ilsa32833566>
  <ilsa32964638>&video;</ilsa32964638>
  <ilsa26214430>0</ilsa26214430>
  <sflags>1</sflags>
 </add>
<!-- netmeeting does add follow by modify -->
 <modify>
  <dn>c=&country;,o=&org;,cn=&email;,objectclass=&class;</dn>
  <sappid>&sappid;</sappid>
  <sappguid>008aff194794cf118796444553540000</sappguid>
  <sprotid>h323</sprotid>
  <sprotmimetype>text/h323</sprotmimetype>
  <sport>&sport;</sport>
 </modify>
</ils>

It might look complicated, but the average user will never need
to alter it. However, if you want to use real LDAP servers, or
override or use some new values, then you can do that without
having to modify GM.

Cheers,

Paul