uucp blows up

[Aron Burns]

We're trying to connect to machines via uucp and having some problems.
a) 'accnt', Xenix 2.3.2, Hayes V-series 2400
b) 'WORK_SWM', SCO UNIX 3.2 ( actually odt ), Telebit t2500 set for 2400

accnt has succesfully uucp'd files from SCO, anomally, my PC ( under
uupc ), and several other systems.  WORK_SWM is a new system ( so I 
suspect it ).

with uutry -x9 accnt from WORK_SWM, the connection starts up, 
login goes ok, a request is made that looks like this

Request: WORK_SW!D.WORK_3fff845 --> accnt!D.WORK_3fff845 (mmdf)

and shortly after this happens

PROCESS: msg - SY
SNDFILE:
send 37777777621
send 37777777631
send 37777777641
send 37777777651
send 37777777761
send 37777777771
-> 317 / 0.100 secs, 3710 bytes/sec
rmesg - 'C' alarm 1
send 37777777621
pkgetpack: Connodata=1
rec h->cntl 41
pkcntl: RR/RJ: Connodata=1
send 37777777631
state - [O.K.] (10)
alarm 2

at which point it appears to try again, with alarm x increasing until
x=8, then it shuts down the connection.

Any thoughts?  WORK_SWM is successfully downloading sls's from SCO, so
uucp seems ok.  I'm sure the config is right ( otherwise it wouldn't
get past login ), and don't know where to go from here.  On  a general
note, what do I read to understand to output from uutry -x9? TFM doesn't
go into detail, nor do the nutshell handbooks.



Aaron Burns      	     "Nothing I say on the net is binding
aronb at gkcl.ists.ca         to our corporation"
Toronto, Ontario         "Life is a forge, and the purest metal
(416)392-4310             comes from the hottest fire"