HN>>> When my IP adres was in the telephone field, where should
 HN>>> my telephone number (POTS + ISDN) to be placed??

 ml>> one of my questions, too...

 HN> So you understand my question;-)

i think so... it seems to be about how a dually connected system can list
their connection methods such that /ALL/ FTN software can find and react to
that information... correct??

 HN>>> IMO using 000-12-456-78-910 in the telephone field should
 HN>>> not be allowed.

 ml>> you have another field in mind that is listed as accepting
 ml>> contact numbers as in FTS-0005??????

 HN> What about:

 HN> Hub,53,fido.ddutch.nl,Heerhugowaard,Kees_van.Eeten,31-72-5723
 HN> 988,9600,CM,XA,MO, V32B,V42B,X75,IBN,IFC,U,ENC
 HN> ,1141,80.100.105.113,Haaksbergen,Herman_Neut,31-53-5724746,96
 HN> 00,XA,CM,X75,V32B, V42B,V34,VFC,IBN,U,ENC
 HN> Pvt,4080,80.56.68.21,Zaltbommel,George_Roubchinsky,-Unpublish
 HN> ed-,300,MO,CM,IBN

 HN> ??

sadly, my domain name and/or IP number are /not/ the name of my system...
my main system is known by its name (aka "title") as
"Waldo's Place USA" in much the same way as echos are known by
their titles instead of their echotags... the "echotag" for my
system could be wplace, wplace.wpusa.dynip.com, 192.168.42.69 or several
other unique indicators that seperate it from the other machines... by
definition, field 3 is to hold the system name... the problem with the
nodelist is that it doesn't lend itself to multiple connection capabilities
by one system unless one uses multiple node numbers and thus multiple
entries... the problem there is that folk start crying wolf and going on
about nodelist stuffing...

)\/(ark