I am trying to set up SEXPOTS for my synchronet BBS (time warp back
to the 90s...). However, sexpots keeps returning "modem command
failure". I am running Debian Bookworm and the U.S. Robotics modem is connected to /dev/ttyS0. The user sbbs is member of the group dialout
and has access tot he modem. I can issue modem commands in mincom and
I am able to connect to the only remaining dialup BBS in my city. So
I confirm that the modem works. I was able to get SEXPOTS to run once yesterday, but since then fails to run (either manually started or
via systemd). I rebooted, restarted the modem etc., not sure how I
managed to get it to run once. After that only failures.
I am trying to set up SEXPOTS for my synchronet BBS (time warp back to the 90s...). However, sexpots keeps returning "modem command failure". I am running Debian Bookworm and the U.S. Robotics modem is connected to /dev/ttyS0. The user sbbs is member of the group dialout and has access tot he modem. I can issue modem commands in mincom and I am able to connect to the only remaining dialup BBS in my city. So I confirm that the modem works. I was able to get SEXPOTS to run once yesterday, but since then fails to run (either manually started or via systemd). I rebooted, restarted the modem etc., not sure how I managed to get it to run once. After that only failures.
Any ideas?
Here is my sexpots.ini
LogLevel = INFO ; set display/log output level
Debug = TRUE ; enable debug logging (overrides LogLevel) PauseOnExit = FALSE ; wait for key-press on exit (non-service)
CLS = FALSE ; send a form feed (clear screen) before copyright banner
Prompt =
PromptTimeout = 60 ; seconds to wait for a remote character after sending prompt (0=infinite)
[COM]
Device = /dev/ttyS0 ; COM port device name (or port number)
BaudRate = 0 ; If non-zero, use this DTE rate (e.g. 115200) Hangup = TRUE ; Hang-up phone after call
IgnoreDCD = FALSE ; Set to TRUE to ignore state of DCD
DCDTimeout = 10 ; Seconds to wait for DCD to drop
DTRDelay = 100 ; Milliseconds to delay before hangup
NullModem = FALSE ; Set to TRUE to not send AT commands to modem Parity = FALSE ; Use parity (error detection/correction) bit ParityOdd = FALSE ; Use odd (not even) parity for parity calculations ByteSize = 8 ; Number of data bits per byte StopBits = 1 ; Number of stop bits per byte
[Modem]
;Init = AT&F ; Modem initialization string
Init = AT&FML1 ; low volume
Thanks Rob.
I also tried AT&F as per your example ini file, but have the same issue.
I even tried an empty Init, no command. Same issue with ATS0=1. This command, as well as AT&F work in minicom.
Maybe I need a longer timeout?
ExecReload=/opt/synchronet/exec/sexpots /opt/synchronet/exec/sexpots.ini -live
/opt/synchronet/exec/sexpots.ini
Re: sexpots.ini - modem command failure (TIMEOUT)
By: HotblackDesiato to Digital Man on Mon Aug 12 2024 23:17:51
/opt/synchronet/exec/sexpots.ini
Weird place to keep a config file. Make friends with your ctrl directory.
Re: sexpots.ini - modem command failure (TIMEOUT)
By: echicken to HotblackDesiato on Tue Aug 13 2024 03:27 pm
Re: sexpots.ini - modem command failure (TIMEOUT)
By: HotblackDesiato to Digital Man on Mon Aug 12 2024 23:17:51
/opt/synchronet/exec/sexpots.ini
Weird place to keep a config file. Make friends with your ctrl
directory.
sexpots doesn't require a Synchronet installation or know anything
about the "ctrl" directory. So it's not so unusual. <shrug>
Right, I have sexpots running out us /usr/local/bin and my config files are in /usr/local/etc - it's all separate from my test sbbs installation.
OK, thanks. What would be the correct "reload" command, please?
I am trying to set up SEXPOTS for my synchronet BBS (time warp back to the 90s...). However, sexpots keeps returning "modem command failure". I am running
Debian Bookworm and the U.S. Robotics modem is connected to /dev/ttyS0. The user sbbs is member of the group dialout and has access tot he modem. I can issue modem commands in mincom and I am able to connect to the only remaining dialup BBS in my city. So I confirm that the modem works. I was able to get SEXPOTS to run once yesterday, but since then fails to run (either manually started or via systemd). I rebooted, restarted the modem etc., not sure how I managed to get it to run once. After that only failures.
Sysop: | Ree |
---|---|
Location: | Toronto, ON |
Users: | 2 |
Nodes: | 10 (0 / 10) |
Uptime: | 02:11:20 |
Calls: | 339 |
Calls today: | 2 |
Files: | 2 |
Messages: | 38,420 |