lenny@icus.UUCP (Lenny Tropiano) (12/30/87)
Recently I've been having *EXTREME* delays in Area code 303 when calling
a particular site. From what I understand they just finished changing
their modems and software to support MNP protocol. Unfortunately UUCP
isn't too forgiving when it comes to delays. I am constantly failing
do to alarm's and BAD READ's.
Does anyone have any idea on how to correct this? I know going through
Telenet there are inherent delays, but I haven't had trouble like this
before. In fact I have about 30 other sites all through PCP and they
aren't causing me any headaches :-(
Telenet has certain parameters I can set using the "SET and PAR" commands.
Is anyone familiar with these and setting the one to increase the window
size will that help? Or will that hurt more!?
Any suggestions/solutions/etc?
-Lenny
--
============================ US MAIL: Lenny Tropiano, ICUS Computer Group
IIIII CCC U U SSSS PO Box 1
I C C U U S Islip Terrace, New York 11752
I C U U SSS PHONE: (516) 968-8576 [H] (516) 582-5525 [W]
I C C U U S AT&T MAIL: ...attmail!icus!lenny TELEX: 154232428
IIIII CCC UUU SSSS UUCP:
============================ ...{uunet!godfre, harvard!talcott}!\
...{ihnp4, boulder, mtune, bc-cis, ptsfa}! >icus!lenny
"Usenet the final frontier" ...{cmcl2!phri, hoptoad}!dasys1!/matt@ncr-sd.SanDiego.NCR.COM (Matt Costello) (12/31/87)
In article <197@icus.UUCP> lenny@icus.UUCP (Lenny Tropiano) writes: >Recently I've been having *EXTREME* delays in Area code 303 when calling >a particular site. From what I understand they just finished changing >their modems and software to support MNP protocol. Unfortunately UUCP >isn't too forgiving when it comes to delays. I am constantly failing >do to alarm's and BAD READ's. To increase the timeout period used by UUCP in the expect/send sequences add delays to the end of your send sequences. This can be used to overcome very long delays. Here is a Honey DanBer example from our Dialers file: # Microcom AX -- modem should be set with the configuration # switches as follows: # # Front: 1 - UP 2 - DN 3 - DN 4 - UP 5 - DN 6 - DN 7 - UP 8 - DN # Back: 1 - DN 2 - UP 3 - DN 4 - UP 5 - DN 6 - DN 7 - DN 8 - ?? # # Since sending an ATZ will cause the modem to drop DCD, we are forced to # explicitly initialize all of the settings we can't reach via the switches. # It's a mess, but it works..... # # Any microcom at 300/1200/2400 mc-direct =W-, "" ATQ0E1\r\c OK\r-ATQ0E1\r\c-OK\r \EATQ0&C0H0\\G0\\N1S0=0\\J1\\Q3\\X1\\K5\r\c OK\r \EATS2=43E1V1\\V1\\E0\\T0%E0\\A3\\C0\r\c OK\r \EAT%A0\\L0\\I0\\H0S8=2&D3&C2\\D0\\R1M3\r\c OK\r \EAT&L0&M0&T5X4&P0&G0B1%D1*E0\r\c OK\r \EATE0DT#2W\T\r\d\d\d\c CONNECT # AX/2400 in reliable mode mc-nmp5 =W-, "" ATQ0E1\r\c OK\r-ATQ0E1\r\c-OK\r \EATQ0&C0H0\\G0\\N3S0=0\\J0\\Q3\\X1\\K5\r\c OK\r \EATS2=43E1V1\\V1\\E0\\T0%E0\\A3\\C0\r\c OK\r \EAT%A0\\L0\\I0\\H0S8=2&D3&C2\\D0\\R1M3\r\c OK\r \EAT&L0&M0&T5X4&P0&G0B1%D1*E0\r\c OK\r \EATE0DT#2W\T\r\d\d\d\c CONNECT # AX/2400c in reliable/compressed mode mc-nmp6 =W-, "" ATQ0E1\r\c OK\r-ATQ0E1\r\c-OK\r \EATQ0&C0H0\\G0\\N3S0=0\\J0\\Q3\\X1\\K5\r\c OK\r \EATS2=43E1V1\\V1\\E0\\T0%E0%C1\\A3\\C0\r\c OK\r \EAT%A0\\L0\\I0\\H0S8=2&D3&C2\\D0\\R1M3\r\c OK\r \EAT&L0&M0&T5X4&P0&G0B1%D1*E0\r\c OK\r \EATE0DT#2W\T\r\d\d\d\c CONNECT The string "\d\d\d\c" adds a delay of 6 seconds before looking for the CONNECT. Since this 6 seconds occurs before UUCP starts looking it effectively adds 6 seconds to the timeout value. The expect/send sequences are broken into multiple lines here to not exceed 80 columns; the original sequences are all on one (very long) line. Each "\d" delays 2 seconds in Honey DanBer UUCP. 30 of them would end up delaying a whole minute, even if the connection occured immediately. In version 2 & BSD UUCP the "\d" delays for 1 second instead. -- Matt Costello <matt.costello@SanDiego.NCR.COM> +1 619 485 2926 <matt.costello%SanDiego.NCR.COM@Relay.CS.NET> {sdcsvax,cbosgd,pyramid,nosc.ARPA}!ncr-sd!matt