lars@iclswe.icl.se (Lars Tunkrans) (04/15/91)
I have tried to call a Trailblazer modem from my Norwegian made Semafor 9696a
V.32 modem. They didnt connect to each other.
Is it reasonable to expect this to work ? I dont know if Trailblazers have
any V.32 capabilites, and the guy I talked to knew even less.
If so, How would you set up the Trailblazer ?
Please email, I dont read this group very often.
Thanks, Lars.
--
Lars Tunkrans Phone +46 (0)76096368. | I C L
DRS Systems Support. |
UUCP: uunet!mcsun!sunic!iclswe!lars | The leading UNIX System V Release 4.0
DOMAIN Address : lars@iclswe.icl.se | integrator.bourman@hpcc01.HP.COM (Bob Bourman) (04/18/91)
/ hpcc01:comp.dcom.modems / lars@iclswe.icl.se (Lars Tunkrans) / 4:56 pm Apr 14, 1991 / >I have tried to call a Trailblazer modem from my Norwegian made Semafor 9696a >V.32 modem. They didnt connect to each other. >Is it reasonable to expect this to work ? I dont know if Trailblazers have >any V.32 capabilites, and the guy I talked to knew even less. >If so, How would you set up the Trailblazer ? >Please email, I dont read this group very often. >Thanks, Lars. >-- >Lars Tunkrans Phone +46 (0)76096368. | I C L DRS Systems Support. | >UUCP: uunet!mcsun!sunic!iclswe!lars | The leading UNIX System V Release 4.0 >DOMAIN Address : lars@iclswe.icl.se | integrator. >---------- I think you have to enable the V.32 option on the TB otherwise it will only connect PEP... There may be another caveat, the time the V.32 modem will wait for the v.32 handshake (3 sec max) and the V.32 modem T1 timer may be set for .03, .08 or 1.6sec and missing the TB V.32 handshake. If I recall, the TB does PEP first and then then V.32. BOBB
john@newave.UUCP (John A. Weeks III) (04/18/91)
In article <1991Apr14.235601.25914@iclswe.icl.se> lars@iclswe.icl.se (Lars Tunkrans) writes: > Is it reasonable to expect this to work ? I dont know if Trailblazers have > any V.32 capabilites, and the guy I talked to knew even less. The T-2500 and T-1600 will talk V.32. The trailblazer is currently documented as not doing V.32. One of the engineers that I work with had great difficulty getting a T-2500 to talk with a standard V.32 modem. It turned out that there was a register setting for enhanced V.32, and our T-2500 somehow got in that setting. -john- -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ John A. Weeks III (612) 942-6969 john@newave.mn.org NeWave Communications ...uunet!tcnet!wd0gol!newave!john
steve@endgame.gsfc.nasa.gov (Steve Rezsutek) (04/20/91)
In article <820011@hpcc01.HP.COM> bourman@hpcc01.HP.COM (Bob Bourman) writes: > I think you have to enable the V.32 option on the TB otherwise > it will only connect PEP... There may be another caveat, the time > the V.32 modem will wait for the v.32 handshake (3 sec max) and > the V.32 modem T1 timer may be set for .03, .08 or 1.6sec and missing > the TB V.32 handshake. If I recall, the TB does PEP first and then > then V.32. > BOBB There is a register (don't recall which one off the top of my head) that controls whether the PEP tones come first or last. I have my chat script set up for `PEP last' when calling a V32 site. Other than that the factory defaults seem fine. Your mileage may vary, of course ;-) Steve
tech@mich-ns.UUCP (Mich. Network Sys. TECH SUPPORT) (04/25/91)
In article <1991Apr14.235601.25914@iclswe.icl.se> lars@iclswe.icl.se (Lars Tunkrans) writes:
"I have tried to call a Trailblazer modem from my Norwegian made Semafor 9696a
"V.32 modem. They didnt connect to each other.
"
"Is it reasonable to expect this to work ? I dont know if Trailblazers have
"any V.32 capabilites, and the guy I talked to knew even less.
"
"If so, How would you set up the Trailblazer ?
"
You don't. The Trailblazer Plus doesn't support V.32. The T1600 supports
V.32 and the T2500 supports both V.32 and PEP. Both support V.42/V.42bis.
--
Michigan Network Systems Technical Support Division
Telebit/SCO/Digiboard Reseller BBS: +1 313 343 0800
1-800-736-5984