I am implementing FILE REQUEST capabilities in an application I
am writing and have been testing my application with the Front
Door Server 2.12.  However I am a bit stumped since I can get
it to work fine and not work at all by making a minor config change
within Front Door.  Bit puzzled as to whether this is something I
am doing wrong or could it be a Front Door problem.

When it works
...----------
If I DISABLE human callers.  Front Door sends me the small System
Down message I instructed Front Door to do and then it processes
the File Request just fine.  Also noticed that it then disables the
NO HUMAN CALLERS flag, not sure why Front Door does this but it does.

= 20:32:14  RING
= 20:32:20  RING
= 20:32:35  CONNECT 14400/ARQ/V42 /SREJ
_ 20:32:37  EMSI Recv: Sent EMSI_REQ
_ 20:32:37  EMSI Recv: Received "EMSI_DAT006E"
_ 20:32:37  EMSI Recv: Fetching EMSI_DAT packet, 110b
_ 20:32:37  EMSI Recv: EMSI_DAT packet OK
_ 20:32:37  EMSI Recv: Sent EMSI_ACK

When it doesn't work
...-----------------
If I leave Human Callers activated.  The Front Door system just
doesn't recognize the EMSI_INQ send.  It sits there for a while
and then shells out to the human caller defined routine.  Only
related setting I noticed was "seconds to wait for human caller",
which I have set at 13 seconds and have even put it higher with
no affect. It both these situations I am making no changes to
my terminal program, why would Front Door recognize the EMSI
command above and not when Human Callers is activated ????

= 20:40:13  RING
= 20:40:19  RING
= 20:40:33  CONNECT 14400/ARQ/V42 /SREJ
+ 20:40:55  Incoming call at 14400 BPS

Has anyone else seen these types of symptoms developing File Request
capabilties ???  Any ideas on what I may possibly need to due prior
to sending EMSI_INQ to take care of this weird symptom ??

72163.3155{at}compuserve.com

--Al

...
 þ OLXWin 1.00b þ Excellent Reference Lists at: http://www.netmation.com

--- RBBSMail/386 v1.0