Subj : Re: sexpots linux modem response timeout To : Ragnarok From : Digital Man Date : Mon Apr 18 2022 10:21:39 Re: Re: sexpots linux modem response timeout By: Ragnarok to Digital Man on Mon Apr 18 2022 10:10 am > El 18/4/22 a las 01:14, Digital Man escribi¢: > > Re: sexpots linux modem response timeout > > By: Ragnarok to DOVE-Net.Synchronet_Discussion on Sun Apr 17 2022 11:26 > > pm > > > > I try to use sexpots with my usrobotics 56k external. > > > the modem work fine with minicom, so no physical connection issues but > > i > > > get a response timeout error. > > > If I set the -null parameter, sexopot starts but i think that i should > > > sent the init string to modem. > > > > > > > > > root@scarlet:/sbbs/exec# ./sexpots -com /dev/ttyS0 > > > > > > Synchronet External POTS Support v2.0-Linux Copyright 2022 Rob > > Swindell > > > > > > 4/17 23:22:20 Synchronet Communications I/O Library for Linux v1.19 > > > 4/17 23:22:20 Build Mar 12 2022 17:24:24 GCC 6.3.0 > > > 4/17 23:22:20 TCP Host: localhost > > > 4/17 23:22:20 TCP Port: 23 > > > 4/17 23:22:20 Opening Communications Device (COM Port): /dev/ttyS0 > > > 4/17 23:22:20 COM Port device handle: 3 > > > 4/17 23:22:20 COM Port DTE rate: 0 bps > > This ^ looks like an issue > > > Try setting the BaudRate in your sexpots.ini file or passing the -baud > > parameter. > > Set the baudrate same results > root@scarlet:/sbbs/exe# ./sexpots ../ctrl/sexpots.modem.ini > > Synchronet External POTS Support v2.0-Linux Copyright 2022 Rob Swindell > > 4/18 09:56:01 Reading sexpots.modem.ini > 4/18 09:56:01 Synchronet Communications I/O Library for Linux v1.19 > 4/18 09:56:01 Build Mar 12 2022 17:24:24 GCC 6.3.0 > 4/18 09:56:01 TCP Host: bbs.docksud.com.ar > 4/18 09:56:01 TCP Port: 23 > 4/18 09:56:01 Opening Communications Device (COM Port): /dev/ttyS0 > 4/18 09:56:01 COM Port device handle: 3 > 4/18 09:56:01 COM Port DTE rate: 57600 bps Does your modem actually support a 57600 DTE rate? Not all modems do. > 4/18 09:56:01 Initializing modem: > 4/18 09:56:01 Modem Command: AT&S1 > 4/18 09:56:02 Waiting for Modem Response ... > 4/18 09:56:07 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0 > 4/18 09:56:07 Retry #1: sending modem command (AT&S1) on /dev/ttyS0 > 4/18 09:56:07 Dropping DTR on /dev/ttyS0 > 4/18 09:56:07 Raising DTR on /dev/ttyS0 > 4/18 09:56:07 Modem Command: AT&S1 > 4/18 09:56:07 Waiting for Modem Response ... > 4/18 09:56:12 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0 > 4/18 09:56:12 Retry #2: sending modem command (AT&S1) on /dev/ttyS0 > 4/18 09:56:12 Dropping DTR on /dev/ttyS0 > 4/18 09:56:12 Raising DTR on /dev/ttyS0 > 4/18 09:56:12 Modem Command: AT&S1 > 4/18 09:56:12 Waiting for Modem Response ... > 4/18 09:56:17 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0 > 4/18 09:56:17 Modem command (AT&S1) failure on /dev/ttyS0 (3 attempts) > 4/18 09:56:17 Cleaning up ... > > > root@scarlet:/sbbs/ctrl# cat sexpots.modem.ini > LogLevel = DEBUG > Debug = TRUE > > [TCP] > Host = bbs.docksud.com.ar > Port = 23 > Telnet = TRUE > NoDelay = TRUE > > [Telnet] > Debug = FALSE > ;TermType = SEXPOTS > TermSpeed = 57600,57600 > > [Modem] > Init = AT&S1 > AutoAnswer = ATS0=1 > Cleanup = ATS0=0 > ;EnableCallerID = AT+VCID=1 > ;Timeout = 15 > Reinit = 60 > ;Answer = ATA > ;Ring = RING > ;ManualAnswer = FALSE > > [COM] > Device = /dev/ttyS0 > Baudrate = 57600 > ;Hangup = TRUE > ;IgnoreDCD = TRUE > ;DCDTimeout = 10 > ;DRTDelay = 100 > ;NullModem = FALSE > > > can you add more debug to this "init" stage? Like what? We're sending commands to the COM port and getting no response. I can't think of what "more debug" to add. -- digital man (rob) Synchronet "Real Fact" #19: The first Synchronet BBS (Vertrauen) went live in July of 1991 (replacing WWIV) Norco, CA WX: 63.8øF, 66.0% humidity, 2 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) .