PE> Correction, Binkley, after reporting "RINGING", and then a
PE> few lines of stats from the connect, decides to swallow the
PE> rest of the lines. When I dialed manually, there were
Actually, it was picking up on the "Error" and deciding it had
an error response from the modem. I modified BTPE to make it
do a case-sensitive comparison, and now I am getting...
> 22 Feb 00:46:58.16 ATDT1456028734491
# 22 Feb 00:47:06.63 RINGING
# 22 Feb 00:47:18.31 Terminal : 57600 8 data bits No Parity
# 22 Feb 00:47:18.35 Line : 26400 V.34
# 22 Feb 00:47:18.38 Error Correct : LAPM
# 22 Feb 00:47:18.41 Compression : V.42bis tx/rx
# 22 Feb 00:47:18.44 Encryption : None
# 22 Feb 00:47:18.47 Current EQM : 009
# 22 Feb 00:47:18.50 EQM Retrain at: 098
# 22 Feb 00:47:18.53 Rx Level(-dBm): 020
# 22 Feb 00:47:18.56 CONNECT 26400/LAP-M/V.42bis/V.34
* 22 Feb 00:47:22.47 Ministry Support Group (3:711/809)
* 22 Feb 00:47:22.47 Remote Uses BinkleyTerm Version 2.59
: 22 Feb 00:47:22.47 Sysop: Dave Hatch
* 22 Feb 00:47:22.50 Password-protected session
: 22 Feb 00:47:22.50 WaZOO method: ZedZap
+ 22 Feb 00:47:22.60 Nothing to send to 3:711/809{at}fidonet
* 22 Feb 00:47:23.28 End of WaZOO Session
* 22 Feb 00:47:23.28 Session with 3:711/809{at}fidonet Time: 00:00:27 Cost: $0.00
> 22 Feb 00:47:24.88 string is ATS42?|
# 22 Feb 00:47:25.69 NO CARRIER
@EOT:
---
* Origin: X (3:711/934.9)
|