Behaviour on TCP disconnect
#7
(05-10-2023, 02:36 PM)ltning Wrote: Hi, sorry for my late reply. Work and life got in the way.

The commands currently being sent during startup/init are:
ATH<CR>
ATZ<CR>
ATS0=0<CR>
AT&D2<CR

For hangup and any other place, ~ represents a 0.5s pause, to allow for the forced return to command mode or other timing sensitive init commands.

Is there any way I can get you a log of what's going on?

The only way to get a "log" is by using a serial sniffer - basically, another computer connected to the same RS232 lines where you can receive what is being transmitted.  There is not enough memory in the WiModem232 to capture a lot of data.

The NO CARRIER message occurs when the Telnet connection is terminated.

ATH doesn't do anything, so you can remove the line if you want. That just means "hang up", which it already is to even be able to enter commands. ATZ resets the settings. ATS0=0 enables auto answer on first "ring". AT&D2 enables hanging up the modem when DTR is toggled. Unless you have a valid reason to do this (like the BBS uses this to hang up on purpose), then I would omit this line. Do you know if the BBS monitors the DCD line to determine if there is a connection? It could be that you have the DCD state backwards?
Reply


Messages In This Thread
Behaviour on TCP disconnect - by ltning - 02-26-2023, 01:47 PM
RE: Behaviour on TCP disconnect - by admin - 02-27-2023, 11:17 AM
RE: Behaviour on TCP disconnect - by ltning - 03-03-2023, 05:38 AM
RE: Behaviour on TCP disconnect - by admin - 03-04-2023, 02:21 PM
RE: Behaviour on TCP disconnect - by ltning - 05-10-2023, 02:36 PM
RE: Behaviour on TCP disconnect - by admin - 05-10-2023, 10:57 PM
RE: Behaviour on TCP disconnect - by ltning - 05-10-2023, 04:52 PM
RE: Behaviour on TCP disconnect - by ltning - 05-12-2023, 04:52 AM
RE: Behaviour on TCP disconnect - by admin - 05-12-2023, 08:40 AM



Users browsing this thread: 1 Guest(s)