(PM) V.42bis on 56K connection?

Joe Hartley (jh@metheny.brainiac.com)
Sat, 20 Jun 1998 14:18:10 -0400 (EDT)

We've got a customer with a SupraExpress 56 (K56Flex) modem who
has experienced the periodic hang (referred to as "data oscillation" by one
person on the list), and provided his pppd log:

Jun 20 13:52:09 bedlam chat[2914]: send (ATDT2438400^M)
Jun 20 13:52:09 bedlam chat[2914]: timeout set to 45 seconds
Jun 20 13:52:09 bedlam chat[2914]: expect (CONNECT)
Jun 20 13:52:09 bedlam chat[2914]: ^M
Jun 20 13:52:33 bedlam chat[2914]: ATDT2438400^M^M
Jun 20 13:52:33 bedlam chat[2914]: CARRIER 42000^M
Jun 20 13:52:35 bedlam chat[2914]: ^M
Jun 20 13:52:35 bedlam chat[2914]: PROTOCOL: LAP-M^M
Jun 20 13:52:35 bedlam chat[2914]: ^M
Jun 20 13:52:35 bedlam chat[2914]: COMPRESSION: V.42BIS^M
Jun 20 13:52:35 bedlam chat[2914]: ^M
Jun 20 13:52:35 bedlam chat[2914]: CONNECT -- got it

The compression protocol of V.42BIS intrigued me - will either V.90 or
K56Flex use this compression successfully?

My guess as to how the protocols are named leads me to conclude that V.42bis
is the compression part of a V.42 connection. If the connection protocol
is _not_ V.42 but V.90 or KFlex, won't the connection go into conniptions
if the compression protocol doesn't match? (And does this mean that we might
see a V.90bis?)

Please enlighten me if I'm far off the trail, but this just doesn't seem
right to me.

========================================================================
Joe Hartley - jh@brainiac.com - brainiac services, inc
PO Box 5069 : Greene, RI : 02827 - vox 401.539.9050 : fax 401.539.2070
Without deviation from the norm, "progress" is not possible. - FZappa
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>