#V.42 Late CONNECT
4 messages in this thread
Not so sure that their behavior is within spec. Think about it, when a
modem is not operating with a fixed DCE/DTE link, the DCE has to send the
connection response to the DTE at the current DCE/DTE link rate and then
shift to the connect rate to pass remote data.
If for only that reason, the modem shouldn't be passing any remote data
until after the connection response code has been sent.
-jack-
Unfortunately, V.42 was done by committee. Appendix I SUGGESTs a couple
of options on what to do with characters rcv'd during negotiation:
a) throw them away
b) buffer them
But it even backs off and saying either of these is an absolute
requirement.
Aren't standards wonderful
.
lGlamb lglamb+RV13@rvdc.unisys.com
CTOS Data Comm Support
Dunno Larry, but based on the dozen or so modems that I've tested here,
Supra got it wrong since none of those modems passes remote data until
after the connection has been established.
Honestly, it is the only reasonable way to handle the situation.
Of course, the reverse side to this is that the remote site should not
begin sending data until after the connection has been established rather
than after DCD goes active. 😉
-jack-
Unfortunately, I don't have control over the remote side in all cases. I
have put out an alert to those I do to add in a delay.
What v.42 modems have you worked with? Maybe I can get a user to spring
for a couple tests units.
lGlamb lglamb+RV13@rvdc.unisys.com
CTOS Data Comm Support