Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!cbnewsm!cbnewsk!njg
From: njg@cbnewsk.att.com (nick.j.gnesda)
Newsgroups: comp.dcom.modems
Subject: Sync Port and V.42 & V.32
Keywords: V.25bis V.42 V.32 Synchronous X.25 Dialing
Message-ID: <1991Apr25.154758.8842@cbnewsk.att.com>
Date: 25 Apr 91 15:47:58 GMT
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 44


I have some questions which I believe ( hope ) others may have 
already developed/devised an answer to. Any help they can offer 
would be greatly appreciated. The questions are specific 
to the V.32 and V.42 ( and their "bis" variants" ) modems. 


	It seems most people use these modems for asynchronous
	communications does anybody use these modems to connect
	to X.25 packet switching networks using synchronous
	ports?

I am not a modem expert by any means but I have read the claims
of various modem manufactures. In general many V.32/V.42 modems
claim synchronous and asynchronous communication capabilities.
Most provide an AT command set for dialing, others in addition 
to the AT command set support a standard called V.25bis, from 
what I can tell by reading some CCITT specs V.25bis defines
a synchronous dialing command set, which replaces the AT commands.
V.25bis can be used by HDLC ( X.25 ) and byte synchronous ( BISYNC ) 
protocols

I wish to establish communications with other computers over
synchronous ports and I would like to use V.42bis modems
which offer some very nice price/performance statistics
but am uncertain as to how to provide the needed dialing
flexibility.

Here's some more questions for any synchronous V.32 and V.42 modem 
users.
	
	If you dial multiple locations and utilize synchronous
	communications in an automated fashion; how are you 
	establishing the modem connection?
	
	Is anyone using V.25bis?

Thank You 
Nick Gnesda
=====================================================================
= Nick Gnesda AT&T-BL 				Place Your Disclaimer
= att mail: hrmso!njg		       			Here
= internet: njg@hrmso.att.com
=====================================================================