• sexpots: Entire modem init string not being sent

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Mon Oct 16 11:13:10 2023
    open https://gitlab.synchro.net/main/sbbs/-/issues/662

    ~~~
    # cat < /dev/ttyACM0 &
    [1] 5532
    root@wibble:~# systemctl start sexpots
    AT&F1s0=0m0l1s48=root@wibble:~#
    ~~~

    As you can see, only part of the init string is sent.

    Init = AT&F1s0=0m0l1s48=7s36=5&W
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Oct 16 11:42:14 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/662#note_4336

    I'm not clear that your method of debug (redirecting the "echo" from the modem) to determine which characters are sent to it is actually correct.

    The log output of sexpots should include an info-level "Modem Command:" message which includes the full command being sent to the com port. You could also use strace or something similar to see the actual "write" command from sexpots and confirm whether or not the full configured init string is being sent.

    Likely unrelated, but the "&W" in your init string (write to NVRAM) is a little unusual. Consider removing that.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Oct 16 12:45:56 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/662#note_4337

    This is going to be a puzzler.

    Running from the command line, no dice.
    ~~~
    root@wibble:/usr/local/etc# /usr/local/bin/sexpots /usr/local/etc/sexpots-line1.ini -syslog=sexpots-line1

    Synchronet External POTS Support v2.0-Linux Copyright 2023 Rob Swindell

    Oct 16 14:38:01 wibble sexpots-line1: Reading /usr/local/etc/sexpots-line1.ini Oct 16 14:38:01 wibble sexpots-line1: Synchronet Communications I/O Library for Linux v1.19
    Oct 16 14:38:01 wibble sexpots-line1: Build Apr 26 2023 17:36:57 GCC 11.3.0
    Oct 16 14:38:01 wibble sexpots-line1: TCP Host: endofthelinebbs.com
    Oct 16 14:38:01 wibble sexpots-line1: TCP Port: 23
    Oct 16 14:38:01 wibble sexpots-line1: Opening Communications Device (COM Port): /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: COM Port device handle: 3
    Oct 16 14:38:01 wibble sexpots-line1: COM Port DTE rate: 0 bps
    Oct 16 14:38:01 wibble sexpots-line1: Initializing modem:
    Oct 16 14:38:01 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:38:01 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Retry #1: sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Dropping DTR on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Raising DTR on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:38:01 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Retry #2: sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:38:01 wibble sexpots-line1: Dropping DTR on /dev/ttyACM0
    Oct 16 14:38:02 wibble sexpots-line1: Raising DTR on /dev/ttyACM0
    Oct 16 14:38:02 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:38:02 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:38:02 wibble sexpots-line1: Modem command (AT&F1s0=0m0l1s48=7s36=5&W) failure on /dev/ttyACM0 (3 attempts)
    Oct 16 14:38:02 wibble sexpots-line1: Cleaning up ...
    Oct 16 14:38:02 wibble sexpots-line1: Done (handled 0 calls).
    ~~~

    Running through strace, different result...

    ~~~
    root@wibble:/usr/local/etc# strace -o f -ff -s 65535 /usr/local/bin/sexpots /usr/local/etc/sexpots-line1.ini -syslog=sexpots-line1

    Synchronet External POTS Support v2.0-Linux Copyright 2023 Rob Swindell

    Oct 16 14:39:24 wibble sexpots-line1: Reading /usr/local/etc/sexpots-line1.ini Oct 16 14:39:24 wibble sexpots-line1: Synchronet Communications I/O Library for Linux v1.19
    Oct 16 14:39:24 wibble sexpots-line1: Build Apr 26 2023 17:36:57 GCC 11.3.0
    Oct 16 14:39:24 wibble sexpots-line1: TCP Host: endofthelinebbs.com
    Oct 16 14:39:24 wibble sexpots-line1: TCP Port: 23
    Oct 16 14:39:24 wibble sexpots-line1: Opening Communications Device (COM Port): /dev/ttyACM0
    Oct 16 14:39:24 wibble sexpots-line1: COM Port device handle: 3
    Oct 16 14:39:24 wibble sexpots-line1: COM Port DTE rate: 0 bps
    Oct 16 14:39:24 wibble sexpots-line1: Initializing modem:
    Oct 16 14:39:24 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:39:24 wibble sexpots-line1: Waiting for Modem Response ...
    Oct 16 14:39:29 wibble sexpots-line1: Modem Response TIMEOUT (5 seconds) on /dev/ttyACM0
    Oct 16 14:39:29 wibble sexpots-line1: Retry #1: sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:39:29 wibble sexpots-line1: Dropping DTR on /dev/ttyACM0
    Oct 16 14:39:29 wibble sexpots-line1: Raising DTR on /dev/ttyACM0
    Oct 16 14:39:29 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:39:29 wibble sexpots-line1: Waiting for Modem Response ...
    Oct 16 14:39:29 wibble sexpots-line1: Modem Response: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:39:29 wibble sexpots-line1: Enabling modem Caller-ID:
    Oct 16 14:39:29 wibble sexpots-line1: Modem Command: AT#CID=1
    Oct 16 14:39:29 wibble sexpots-line1: Waiting for Modem Response ...
    Oct 16 14:39:30 wibble sexpots-line1: Modem Response: OK
    Oct 16 14:39:30 wibble sexpots-line1: Waiting for incoming call (Ring Indication) ...
    ~~~

    the log looks something like this...

    ~~~
    sendto(4, "<14>Oct 16 14:39:24 sexpots-line1: Opening Communications Device (COM Port): /dev/ttyACM0", 89, MSG_NOSIGNAL, NULL, 0) = 89
    openat(AT_FDCWD, "/dev/ttyACM0", O_RDWR|O_NONBLOCK) = 3
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, SNDCTL_TMR_START or TCSETS, {B0 -opost -isig -icanon -echo ...}) = 0 ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    sendto(4, "<14>Oct 16 14:39:24 sexpots-line1: COM Port device handle: 3", 60, MSG_NOSIGNAL, NULL, 0) = 60
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, SNDCTL_TMR_START or TCSETS, {B0 -opost -isig -icanon -echo ...}) = 0 ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, SNDCTL_TMR_START or TCSETS, {B0 -opost -isig -icanon -echo ...}) = 0 ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B0 -opost -isig -icanon -echo ...}) = 0
    sendto(4, "<14>Oct 16 14:39:24 sexpots-line1: COM Port DTE rate: 0 bps", 59, MSG_NOSIGNAL, NULL, 0) = 59
    ioctl(3, TIOCMBIS, [TIOCM_DTR]) = 0
    sendto(4, "<14>Oct 16 14:39:24 sexpots-line1: Initializing modem:", 54, MSG_NOSIGNAL, NULL, 0) = 54
    sendto(4, "<14>Oct 16 14:39:24 sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W", 75, MSG_NOSIGNAL, NULL, 0) = 75
    write(3, "A", 1) = 1
    write(3, "T", 1) = 1
    write(3, "&", 1) = 1
    write(3, "F", 1) = 1
    write(3, "1", 1) = 1
    write(3, "s", 1) = 1
    write(3, "0", 1) = 1
    write(3, "=", 1) = 1
    write(3, "0", 1) = 1
    write(3, "m", 1) = 1
    write(3, "0", 1) = 1
    write(3, "l", 1) = 1
    write(3, "1", 1) = 1
    write(3, "s", 1) = 1
    write(3, "4", 1) = 1
    write(3, "8", 1) = 1
    write(3, "=", 1) = 1
    write(3, "7", 1) = 1
    write(3, "s", 1) = 1
    write(3, "3", 1) = 1
    write(3, "6", 1) = 1
    write(3, "=", 1) = 1
    write(3, "5", 1) = 1
    write(3, "&", 1) = 1
    write(3, "W", 1) = 1
    clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=100000000}, 0x7ffef742a9b0) = 0
    ioctl(3, TCFLSH, TCIFLUSH) = 0
    write(3, "\r", 1) = 1
    sendto(4, "<15>Oct 16 14:39:24 sexpots-line1: Waiting for Modem Response ...", 65, MSG_NOSIGNAL, NULL, 0) = 65
    ~~~
    Then I get 60,000 lines of

    ~~~
    read(3, 0x7ffef742a98f, 1) = -1 EAGAIN (Resource temporarily unavailable)
    clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=1000000}, 0x7ffef742aa60) = 0
    ~~~

    However, as we've seen the resource is (or should be) available.


    Running through service, yet a different result:

    ~~~
    root@wibble:/usr/local/etc# systemctl start sexpots-line1
    Oct 16 14:44:10 wibble systemd[1]: Started sexpots-line1.service.
    Oct 16 14:44:10 wibble sexpots-line1: Reading /usr/local/etc/sexpots-line1.ini Oct 16 14:44:10 wibble sexpots-line1: Synchronet Communications I/O Library for Linux v1.19
    Oct 16 14:44:10 wibble sexpots-line1: Build Apr 26 2023 17:36:57 GCC 11.3.0
    Oct 16 14:44:10 wibble sexpots-line1: TCP Host: endofthelinebbs.com
    Oct 16 14:44:10 wibble sexpots-line1: TCP Port: 23
    Oct 16 14:44:10 wibble sexpots-line1: Opening Communications Device (COM Port): /dev/ttyACM0
    root@wibble:/usr/local/etc# Oct 16 14:44:10 wibble sexpots-line1: COM Port device handle: 3
    Oct 16 14:44:10 wibble sexpots-line1: COM Port DTE rate: 0 bps
    Oct 16 14:44:10 wibble sexpots-line1: Initializing modem:
    Oct 16 14:44:10 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:44:10 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:44:10 wibble sexpots-line1: Retry #1: sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:44:10 wibble sexpots-line1: Dropping DTR on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Raising DTR on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:44:11 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Retry #2: sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Dropping DTR on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Raising DTR on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Modem Command: AT&F1s0=0m0l1s48=7s36=5&W Oct 16 14:44:11 wibble sexpots-line1: ERROR 11 sending modem command (AT&F1s0=0m0l1s48=7s36=5&W) on /dev/ttyACM0
    Oct 16 14:44:11 wibble sexpots-line1: Modem command (AT&F1s0=0m0l1s48=7s36=5&W) failure on /dev/ttyACM0 (3 attempts)
    Oct 16 14:44:11 wibble sexpots-line1: Cleaning up ...
    Oct 16 14:44:11 wibble sexpots-line1: Done (handled 0 calls).
    Oct 16 14:44:11 wibble sexpots[31739]: Synchronet External POTS Support v2.0-Linux Copyright 2023 Rob Swindell
    Oct 16 14:44:11 wibble systemd[1]: sexpots-line1.service: Deactivated successfully.
    ~~~

    So I'm at a bit of a loss as to what is happening here.

    I run minicom with minicom -D /dev/ttyACM0
    and then send the command

    ~~~
    Welcome to minicom 2.8

    OPTIONS: I18n
    Port /dev/ttyACM0, 14:44:10

    Press CTRL-A Z for help on special keys

    AT&F1s0=0m0l1s48=7s36=5&W
    OK

    OK
    ~~~

    Works fine.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Oct 16 13:59:55 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/662#note_4338

    The strace output shows that the entire init string is being sent to the com port by sexpots.

    So the issue description "Entire modem init string not being sent" is not actually happening.

    If the actual question you wanted to ask was: why I am getting an "ERROR 11 sending modem command" or what does that error mean? That would be a different issue.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Oct 16 14:05:02 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/662#note_4339

    Can't be arsed. Just going to close it.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Mon Oct 16 14:05:02 2023
    close https://gitlab.synchro.net/main/sbbs/-/issues/662
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Oct 16 15:04:11 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/662#note_4340

    Error 11 is EAGAIN ("Try again") - for which there is no retry/loop in sexpots today. I could add one, thought I'm not sure it'd solve this issue. Might be worth an experiment.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Charles Blackburn@1:103/705 to Nigel Reed on Tue Oct 17 07:30:41 2023
    Re: sexpots: Entire modem init string not being sent
    By: Nigel Reed to GitLab issue in main/sbbs on Mon Oct 16 2023 11:13:10

    open https://gitlab.synchro.net/main/sbbs/-/issues/662
    root@wibble:~# systemctl start sexpots
    AT&F1s0=0m0l1s48=root@wibble:~#

    i would be concerned about the catting of the device, that is well known way back in the day for losing characters
    the logfile has the actual init commands logged etc in there

    10/17 07:27:00 Opening Communications Device (COM Port): /dev/ttyS0
    10/17 07:27:00 COM Port device handle: 3
    10/17 07:27:00 COM Port DTE rate: 115200 bps
    10/17 07:27:00 Initializing modem:
    10/17 07:27:00 Modem Command: AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1
    10/17 07:27:00 Ident server thread started


    As you can see, only part of the init string is sent.
    Init = AT&F1s0=0m0l1s48=7s36=5&W

    i have found that if you have a space in your init command, that it stops at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol

    here's mine for reference. i'm of the old school way of init everything that you want even if it's
    stored in nvram. I have had experience with modems way back when that would never read from the nvram
    for whatever reason wen they booted up so you had to init everything

    Init = AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string

    charlie

    ---
    þ Synchronet þ The FBO BBS - IPV4/V6 - bbs.thefbo.us or bbs6.thefbo.us
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Charles Blackburn on Tue Oct 17 10:56:18 2023
    Re: sexpots: Entire modem init string not being sent
    By: Charles Blackburn to Nigel Reed on Tue Oct 17 2023 07:30 am

    Re: sexpots: Entire modem init string not being sent
    By: Nigel Reed to GitLab issue in main/sbbs on Mon Oct 16 2023 11:13:10

    open https://gitlab.synchro.net/main/sbbs/-/issues/662
    root@wibble:~# systemctl start sexpots
    AT&F1s0=0m0l1s48=root@wibble:~#

    i would be concerned about the catting of the device, that is well known way back in the day for losing characters
    the logfile has the actual init commands logged etc in there

    10/17 07:27:00 Opening Communications Device (COM Port): /dev/ttyS0
    10/17 07:27:00 COM Port device handle: 3
    10/17 07:27:00 COM Port DTE rate: 115200 bps
    10/17 07:27:00 Initializing modem:
    10/17 07:27:00 Modem Command: AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1
    10/17 07:27:00 Ident server thread started


    As you can see, only part of the init string is sent.
    Init = AT&F1s0=0m0l1s48=7s36=5&W

    i have found that if you have a space in your init command, that it stops at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol

    That shouldn't be the case. Are you sure about that?
    --
    digital man (rob)

    Sling Blade quote #26:
    Karl: kaiser blade, ax handle with long blade on it shaped kinda like a banana. Norco, CA WX: 77.3øF, 53.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Charles Blackburn@1:103/705 to Digital Man on Tue Oct 17 16:44:09 2023
    Re: sexpots: Entire modem init string not being sent
    By: Digital Man to Charles Blackburn on Tue Oct 17 2023 10:56:18

    Re: sexpots: Entire modem init string not being sent
    By: Charles Blackburn to Nigel Reed on Tue Oct 17 2023 07:30 am
    Re: sexpots: Entire modem init string not being sent
    By: Nigel Reed to GitLab issue in main/sbbs on Mon Oct 16 2023 11:13:10

    <CUT>

    i have found that if you have a space in your init command, that it stops at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol

    That shouldn't be the case. Are you sure about that?

    yup.... for sure

    for example


    sbbs@wwiv:~/ctrl$ diff sexpots.ini sexpots_tst.ini
    18c18
    < Init = AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string
    -+-
    Init = AT&F+VCID=1 +ipr=115200 $sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string


    first one is the working one, second is the one that stops. AGAIN, NOT a big deal, just a personal bugbear that I prefer spaces between the parameters LOL

    this is the log from the second one:

    10/17 16:41:08 Opening Communications Device (COM Port): /dev/ttyS0
    10/17 16:41:08 COM Port device handle: 3
    10/17 16:41:08 COM Port DTE rate: 115200 bps
    10/17 16:41:08 Initializing modem:
    10/17 16:41:08 Modem Command: AT&F+VCID=1
    10/17 16:41:08 Ident server thread started


    Charlie

    ---
    þ Synchronet þ The FBO BBS - IPV4/V6 - bbs.thefbo.us or bbs6.thefbo.us
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Charles Blackburn on Tue Oct 17 18:23:04 2023
    Re: sexpots: Entire modem init string not being sent
    By: Charles Blackburn to Digital Man on Tue Oct 17 2023 04:44 pm

    Re: sexpots: Entire modem init string not being sent
    By: Digital Man to Charles Blackburn on Tue Oct 17 2023 10:56:18

    Re: sexpots: Entire modem init string not being sent
    By: Charles Blackburn to Nigel Reed on Tue Oct 17 2023 07:30 am
    Re: sexpots: Entire modem init string not being sent
    By: Nigel Reed to GitLab issue in main/sbbs on Mon Oct 16 2023 11:13:10

    <CUT>

    i have found that if you have a space in your init command, that it stops at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol

    That shouldn't be the case. Are you sure about that?

    yup.... for sure

    for example


    sbbs@wwiv:~/ctrl$ diff sexpots.ini sexpots_tst.ini
    18c18
    < Init = AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string
    -+-
    Init = AT&F+VCID=1 +ipr=115200 $sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string


    first one is the working one, second is the one that stops. AGAIN, NOT a big deal, just a personal bugbear that I prefer spaces between the parameters LOL

    this is the log from the second one:

    10/17 16:41:08 Opening Communications Device (COM Port): /dev/ttyS0
    10/17 16:41:08 COM Port device handle: 3
    10/17 16:41:08 COM Port DTE rate: 115200 bps
    10/17 16:41:08 Initializing modem:
    10/17 16:41:08 Modem Command: AT&F+VCID=1
    10/17 16:41:08 Ident server thread started

    Ah, indeed that does appear to be intentional: https://gitlab.synchro.net/main/sbbs/-/commit/af86e3d56b8d163abced1223c881cbb8 --
    digital man (rob)

    Synchronet/BBS Terminology Definition #40:
    HTTPS = Secure HTTP (authenticated and encrypted HTTP over TLS)
    Norco, CA WX: 77.4øF, 47.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From fusion@1:103/705 to Charles Blackburn on Wed Oct 18 09:52:00 2023
    On 17 Oct 2023, Charles Blackburn said the following...

    i have found that if you have a space in your init command, that it at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol

    That shouldn't be the case. Are you sure about that?


    sbbs@wwiv:~/ctrl$ diff sexpots.ini sexpots_tst.ini
    18c18
    < Init = AT&F+VCID=1+ipr=115200$sb115200%C1\N3+DCS=1,1+DR=1 ; Modem initialization string
    -+-
    Init = AT&F+VCID=1 +ipr=115200 $sb115200%C1\N3+DCS=1,1+DR=1 ; Mo initialization string


    sexpots.c:

    iniGetExistingWord() -> iniGetExistingString -> FIND_WHITESPACE(value) -> first space replaced with 0

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    # Origin: cold fusion - cfbbs.net - grand rapids, mi
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From fusion@1:103/705 to Digital Man on Wed Oct 18 09:54:00 2023
    On 17 Oct 2023, Digital Man said the following...

    Ah, indeed that does appear to be intentional: https://gitlab.synchro.net/main/sbbs/-/commit/af86e3d56b8d163abced1223c881

    d'oh.. i need to start polling qwk packets before i respond to anything lol

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    # Origin: cold fusion - cfbbs.net - grand rapids, mi
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Charles Blackburn@1:103/705 to fusion on Wed Oct 18 16:24:56 2023
    Re: Re: sexpots: Entire modem init string not being sent
    By: fusion to Charles Blackburn on Wed Oct 18 2023 09:52:00

    On 17 Oct 2023, Charles Blackburn said the following...

    i have found that if you have a space in your init command, that it at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol
    <CUT>

    sexpots.c:

    iniGetExistingWord() -> iniGetExistingString -> FIND_WHITESPACE(value) -> first space replaced with 0

    or you could just "split the string between the '=' and the ';' or EOL and send that :D

    Charlie

    ---
    þ Synchronet þ The FBO BBS - IPV4/V6 - bbs.thefbo.us or bbs6.thefbo.us
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Charles Blackburn on Wed Oct 18 18:30:25 2023
    Re: Re: sexpots: Entire modem init string not being sent
    By: Charles Blackburn to fusion on Wed Oct 18 2023 04:24 pm

    Re: Re: sexpots: Entire modem init string not being sent
    By: fusion to Charles Blackburn on Wed Oct 18 2023 09:52:00

    On 17 Oct 2023, Charles Blackburn said the following...

    i have found that if you have a space in your init command, that it at the whitespace. no big deal but
    took me a couple of minutes to figure that one out lol
    <CUT>

    sexpots.c:

    iniGetExistingWord() -> iniGetExistingString -> FIND_WHITESPACE(value) -> first space replaced with 0

    or you could just "split the string between the '=' and the ';' or EOL and send that :D

    Could, but I think a semicolon could be part of a valid AT command too. Probably best to leave it the way it is.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #63:
    REP = QWK Reply
    Norco, CA WX: 80.3øF, 45.0% humidity, 3 mph S wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)