ISODE, TLI, and OSI stack

[Jason Cross <[e-mail]>]

Our site is porting quipu and the ftp/ftam gateway to operate over
the full OSI stack [Retix] via TLI.  We were successfull with the
ftp/ftam gway, but are having a few problems with quipu.  Any help/
hints will be appreciated.

For testing, the example in ~isode/others/quipu/quipu-db/organisation
is being used.  The syntax and value of the Presentation address in
c=GB/EDB is:

      presentationAddress= '025c'H/NS+4900010000C085C45801

This value is also in dsaptailor:

      dsa_address toucan      '025c'H/NS+4900010000C085C45801


Is the syntax proper, and is the value for TSAP ('025c') okay?  I did not
see an example in the documentation, but found one in the sample EDB.


This is the output after starting ros.quipu:

   # ./ros.quipu

   Tailor LOGDIR /usr/isode-8.0-tli/tmp
   Tailor Rootdir /usr2/isode-8.0-tli/etc/quipu-db/
   Tailor Update off
   Tailor search level 2
   Tailor last modified on
   Tailor DSPChaining on
   Tailor admin size 100
   Tailor admin time 60
   Tailor cache time 21600
   Tailor conn time 300
   Loading oid table (/usr2/isode-8.0-tli/etc/oidtable)
   About to dsa_init()
   Process size = 4808704 bytes
   dsa name c=GB@CN=toucan
   No DSA pseudo entry: "/usr2/isode-8.0-tli/etc/quipu-db/DSA.pseudo" (2)
   DSA.real entry inconsistent with EDB -- problem should fix itself later!
   Loading "/usr2/isode-8.0-tli/etc/quipu-db/c=GB/EDB"
   Loading "/usr2/isode-8.0-tli/etc/quipu-db/c=GB/o=XX/EDB"
   Loading "/usr2/isode-8.0-tli/etc/quipu-db/c=GB/o=XX/CS/EDB"
   Net Starting
   Using community 1 for external access
   Using community 3 for external access
   Using community 99 for external access
   Using community 98 for external access
   Using community 97 for external access
   DSA c=GB@CN=toucan has started on '025c'H/LOCAL++x00010000c085c45801
   DSA c=GB@CN=toucan has started on '025c'H/LOCAL++x00010000c085c45801
   Start size = 5136384 bytes
   Listening for new associations
   Not making new associations
   secs: -1; nads: 0; iads 0x0, wads 0x0
   

This is the output from ros.quipu when attempting to connect with
dish:

   Connection 4, ? OPENING
   From: NULLPA
   Process grown by 8192 bytes
   Listening on ads:  4.
   Not making new associations
   secs: 45; nads: 5; iads 0x10, wads 0x0
   Connection 4, ? OPENING
   From: NULLPA
   conn_rel_abort 4
   RO-ABORT-BIND.REQUEST called on 4
   DSAP user abort (4), ABORT (RO BIND): invalid association descriptor 
      (Error in RO-BIND)
   conn_extract
   checking connlist
   Extracting conn from connlist
   conn_free()
   Listening for new associations
   Not making new associations
   secs: 45; nads: 0; iads 0x0, wads 0x0
   Listening for new associations
   Not making new associations
   secs: -1; nads: 0; iads 0x0, wads 0x0
   TNetAccept: [Protocol error]
   Listening for new associations
   Not making new associations
   secs: -1; nads: 0; iads 0x0, wads 0x0


This is the output after running dish:

   # ./dish -c toucan
   
   Welcome to Dish (DIrectory SHell)
   *** Service error : Unavailable ***
   (Protocol error at transport)


ciao,
Jason Cross
EDS
Troy, Mi.