km@mathcs.emory.edu (Ken Mandelberg) (11/03/90)
We are having some problems connecting to some new rackmount T2500
modems running Version GE7.00-T2500RM firmware. These modems are
setup to offer V.32 tones first (S92=1) and PEP at the end.
The problem I have first hand knowledge of is trying to connect
to these with a T2000 that wants a PEP connection (S50=255).
The T2000 waits patiently thrrough the V.32 and V.22 offerings,
but for some reason doesn't take the bait when the PEP tones
finally appear. Its not a timeout issue either, if I raise S7
above the default, it waits through the PEP offerings and holds
on listening to the dead air after the T2500 has tried everything.
The same T2000 has no problem making PEP connection to the other
T2500s in the T2500 rack. These are a bit older T2500s running
Version GA2.00 firmware. As it happens the older modems are
set for PEP first S92=0, so that is an extra variable.
To my ear the PEP tones offered by the GE7.00 modems at the end
of the sequence sound a little different than the PEP tones
I hear on the older GA2.00 modems. It sound to me like the PEP
tones have an extra "lilt" at the beginning. I could be wrong.
Does this sound familiar to anyone?
***
The V.32 users with non Telebit modems say they have trouble
connecting in V.32 mode. They say the T2500 hangs up on them.
I didn't notice this myself when I tried a USR Courier V.32
against them, but there are a lot of variables. Still, since
the T2500's are offering V.32 first, I'm surprised that V.32
modems are having trouble. The problems I have heard expressed
in the past were with non Teletbits getting confused when the
PEP tones came first.
Any ideas on what may be bothering the V.32's?
I'll include the GE7.00 register settings, in case anyone see's
somethings odd in them:
E1 F1 Q4 T V1 W0 X1 Y0 &P0 &T4 Version GE7.00-T2500RM
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
S10=007 S11=070 S12=050 S18=000 S25=005 S26=000 S38=000
S41=000 S45:255 S47:008 S48=000 S49=000
S50=000 S51:005 S52:002 S54:002 S55=000 S56=017 S57=019 S58:002 S59=000
S61=150 S62=003 S63=001 S64=000 S65=000 S66:001 S67=000 S68:002 S69=000
S90=000 S91=000 S92:001 S93=008 S94=001 S95:002 S96=001 S97=000 S98=003
S100=000 S101=000 S102=000 S103=000 S104=000 S105=001 S106=000 S107=020
S110=255 S111=255 S112=001
S121=000 S130:003 S131:001
S150=000 S151=004 S152=001 S153=001 S154=000 S155=000 S157=000 S158=000
S160=010 S161=020 S162=002 S163=003 S164=007 S169=000 S255:001
--
Ken Mandelberg | km@mathcs.emory.edu PREFERRED
Emory University | {rutgers,gatech}!emory!km UUCP
Dept of Math and CS | km@emory.bitnet NON-DOMAIN BITNET
Atlanta, GA 30322 | Phone: (404) 727-7963bruce@zuhause.MN.ORG (Bruce Albrecht) (11/03/90)
I had the same problem, although I have noticed that the T2000 will not respond to 2400 baud carrier tones after hearing the V.32 carrier, as well as the PEP. I talked to Telebit, and they sent me BC5.10A ROMs which cured the V.32/PEP problem. I'm not convinced that it's fixed the V.32/2400 baud problem, though. -- bruce@zuhause.mn.org
cec@cup.portal.com (Cerafin E Castillo) (11/03/90)
Ken,
The GE7.00 firmware has a new twist to the PEP tones,
a constant tone to deal with echo suppressors used in MCI/Sprint
long distance carrier service. This extra tone may be giving
some older modems a hard time. Call tech support at TELEBIT
and let them know about this. Hold out for a BC5.01 firmware
upgrade to your T2000. This may fix it. TELEBIT is supposed
to be testing new releases so this doesn't happen, but buggy
firmware still slips through. Good Luck!
===============================================================================
Cerafin E. Castillo || //\\ ||\\ ||
Network Consultant || //__\\ || \\ || Los Altos
Los Altos Networks || // ---\\|| \\|| Networks
340 Second St. #6 ||___// \|| \\|
Los Altos, CA 94022
(415) 941-8031 UUCP: {apple,sun,uunet}!portal!cup.portal.com!cec
NTERNET: cec@cup.portal.com
"...No hay mal que por bien no venga..."
===============================================================================david@monymsys.uucp (David Kozinn) (11/06/90)
In article <6480@emory.mathcs.emory.edu> km@mathcs.emory.edu (Ken Mandelberg) writes: >We are having some problems connecting to some new rackmount T2500 >modems running Version GE7.00-T2500RM firmware. These modems are >setup to offer V.32 tones first (S92=1) and PEP at the end. > >The problem I have first hand knowledge of is trying to connect >to these with a T2000 that wants a PEP connection (S50=255). >The T2000 waits patiently thrrough the V.32 and V.22 offerings, >but for some reason doesn't take the bait when the PEP tones >finally appear. As someone else noted, there is a register that controls echo surpression when running on the SPRINT phone system. I had the same problem described (though it was a T2500 that couldn't connect to Trailblazer Plus modems with a ROM revision less than 5.00), and the fix was to set register 120 to 16 (using ATS120=16&Wx). Apparently, there may be some problems if you call out or in using SPRINT, but my company uses SPRINT for it's long distance calling and I haven't seen any problems (yet!) If you find problems on outgoing call, you could always put ATS120=0 as part of your dialing string. >The V.32 users with non Telebit modems say they have trouble >connecting in V.32 mode. They say the T2500 hangs up on them. > >Any ideas on what may be bothering the V.32's? I had problems with a Hayes Ultra V-series before I reversed the tones (to PEP last). The Hayes decided to connect at 300 baud (!) for some unknown reason. I was able to fix this pretty easily by changing the Hayes' dial script to include ATN0S37=9, which forces a 9600 baud connect. Obviously, this will differ if you're using a different modem. -- David Kozinn | UUCP: uunet!vmp!monymsys!david MONY Financial Services MD 75-14 | Domain: monymsys!david@vmp.com Glenpointe Centre West | GEnie: D.KOZINN Teaneck, NJ 07666-6888 | Phone: +1-201-907-6990