TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 18ed5ab2   
   REPLY: 2:201/137 52230099   
   TZUTC: -0400   
    BW> Are you suggesting that Mystic can be launched right away from mgetty   
    BW> instead? If so, do you have some example /etc/mgetty/login.config   
    BW> snippets for this?   
      
   Yes that is what I am suggesting :)   
      
   No I don't have examples.  I don't have a modem or any way to test or maintain   
   modem code, so that is why I don't have any documentation or native modem   
   answering in Mystic anymore.   
      
   The login.config file itself I believe tells you how to set what is executed   
   upon connection so I would look there.  You could add -ST3 into Mystic so it   
   shows MODEM as the connection type.  You could use -IP or -HOST options on the   
   command line to pass in caller ID information that will show up using the IP   
   and HOST MCI codes and this will be tracked in the user records as well.   
      
   You can do a similar thing to handle AX.25 packet radio to Mystic   
      
   ... You can learn many things from children... like how much patience you have   
      
   --- Mystic BBS v1.12 A47 2021/08/17 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 19/10 90/1 103/705 105/81 120/340 457 616 123/10 131   
   SEEN-BY: 124/5016 129/215 305 154/10 30 40 50 700 203/0 220/80 90   
   SEEN-BY: 221/0 1 6 242 360 226/18 30 227/114 201 702 229/310 424 426   
   SEEN-BY: 229/428 452 550 700 981 1016 1017 230/0 240/5832 249/206   
   SEEN-BY: 249/307 317 400 280/464 5003 282/1038 292/854 8125 301/1   
   SEEN-BY: 317/3 320/219 322/757 342/200 396/45 423/81 633/267 280 281   
   SEEN-BY: 633/410 412 414 416 509 640/1138 1321 1384 712/848 770/1   
   SEEN-BY: 2452/250 3634/12   
   PATH: 129/215 154/10 280/464 221/1 640/1384 633/280 229/426