RS> I'm basically asking if the more detailed diag display at your
RS> end on what got negotiated has anything useful on that stuff.

PE> What makes you think that this isn't normal
PE> bad lines, modems doing their EC business?

Cant be that because you are thinking in terms of the possibility
that the lines between here and Sydney etc vary, they dont. My line
gets digitised in the line card at my exchange and goes on the fibre
optic cable to Sydney, to your exchange basically, and then its converted
to analog again at your end and out the copper pair to your unit.

That means that in a practical sense its now only the line from my
house to the exchange and your unit to your exchange that can vary.

The results are just too consistent for it to be that, the entire session
has the same low thruput, none of the bursty display on the modem lights that
should be seen if the modems are furiously retransmitting all the time due to
errors, and the two dud sessions have the SAME thruput which is dramatically
worse than usual. It wouldnt be that consistent if it was line errors.

PE> Obviously with the bad lines starting after the
PE> connect, because the connect has a great EQM.

The call is supposed to fall back line
speed wise if the EQM goes bad. It doesnt.

The other weird thing is that the upload to you gets the SAME
speed with the uncompressed file as the downloads from you get.
Even tho your logs clearly show that V42bis has been achieved,
and thats also shown on the front of my modem. Must be something
pretty weird about the session to produce THAT result, the same
thruput for a compressed and very compressible file.

Turns out the problem was at my end.

I dial normal phone numbers for voice calls with the modem, and THAT
dialer does that at 9600. Must be some quirk where Frodo and X00 dont
manage to seize the port speed back at the 38400 that I have setup in Frodo.

I have just confirmed that by deliberately making a call at 16:20 Monday
after using the voice number dialler, and got that low thruput and the
same characteristic display on the lights on the front of the modem.

The couple of dud calls before that was me too. Frodo appears to
belt on the modem/fossil between calls. The first one could clearly
be seen to connect to you ok, but my mailer wasnt seeing anything
from the modem connect text wise. So, after it had aborted that call,
it appears to belt on the modem or the fossil to get the port speed
sorted out at 9600. So the next call after that is done at 9600 port
speed to give the lousy thruput and characteristic symptoms. Presumably
usually Frodo would belt on the modem/fossil as part of its periodic
heartbeat check of the modem after the use of it for dialing a voice
number, so normal mail runs dont produce the failed call first.

Yet another example of the usefulness of a modem with a
decent status display on the front of the modem too |-)
@EOT:

---