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
4/17 23:22:20 Initializing modem:
4/17 23:22:20 Modem Command: AT&F
4/17 23:22:25 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:25 Retry #1: sending modem command (AT&F) on /dev/ttyS0
4/17 23:22:25 Modem Command: AT&F
4/17 23:22:30 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:30 Retry #2: sending modem command (AT&F) on /dev/ttyS0
4/17 23:22:30 Modem Command: AT&F
4/17 23:22:35 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:35 Modem command (AT&F) failure on /dev/ttyS0 (3 attempts)
4/17 23:22:35 Cleaning up ...
4/17 23:22:35 Done (handled 0 calls).


Welcome to minicom 2.7.1

OPCIONES: I18n
Compilado en May 6 2018, 08:02:47.
Port /dev/ttyS0, 23:22:25

Presione CTRL-A Z para obtener ayuda sobre teclas especiales

atz
OK
ati3
U.S. Robotics 56K FAX EXT V5.1.4

OK

---
￭ Synchronet ￭ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

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.
--
digital man (rob)

Sling Blade quote #11:
Doyle Hargraves (to Karl): What in the hell you doin' with that hammer?
Norco, CA WX: 61.4°F, 69.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrs ---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net

On Sun, 17 Apr 2022 23:26:35 -0300
"Ragnarok" <ragnarok@VERT/DOCKSUD> wrote:

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
4/17 23:22:20 Initializing modem:
4/17 23:22:20 Modem Command: AT&F
4/17 23:22:25 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:25 Retry #1: sending modem command (AT&F) on /dev/ttyS0
4/17 23:22:25 Modem Command: AT&F
4/17 23:22:30 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:30 Retry #2: sending modem command (AT&F) on /dev/ttyS0
4/17 23:22:30 Modem Command: AT&F
4/17 23:22:35 Modem Response TIMEOUT (5 seconds) on /dev/ttyS0
4/17 23:22:35 Modem command (AT&F) failure on /dev/ttyS0 (3 attempts)
4/17 23:22:35 Cleaning up ...
4/17 23:22:35 Done (handled 0 calls).

Welcome to minicom 2.7.1

OPCIONES: I18n
Compilado en May 6 2018, 08:02:47.
Port /dev/ttyS0, 23:22:25

Presione CTRL-A Z para obtener ayuda sobre teclas especiales

atz
OK
ati3
U.S. Robotics 56K FAX EXT V5.1.4

OK

You're not still running minicom while starting up sexpots are you, or
is something else maybe holding your tty device open?

If I have minicom running and try to start sexpots then the
initialization command is echoed there and not back to sexpots.

use losof of fuser on your /dev/ttyS0 device and see what else might be
using the device.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
---
■ Synchronet ■ End Of The Line BBS - endofthelinebbs.com

You're not still running minicom while starting up sexpots are you, or
is something else maybe holding your tty device open?

If I have minicom running and try to start sexpots then the
initialization command is echoed there and not back to sexpots.

use losof of fuser on your /dev/ttyS0 device and see what else might be
using the device.

Hi Nelgin!

I'm pretty sure that no other process are using and lock the port, modem
are working (I can establish connections using minicom)

Nullmodem cable with another computer also work. So no hardware problems related.

root@scarlet:/sbbs/ctrl# setserial /dev/ttyS0
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4

lsof output was empty:

root@scarlet:/sbbs/ctrl# lsof|grep ttyS0
root@scarlet:/sbbs/ctrl#

---
￭ Synchronet ￭ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

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
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?

---
￭ Synchronet ￭ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

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. <shrug>
--
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 ---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net