12-03-2024, 01:56 AM
After looking at this, I think the proper way to handle this would be to insert the caller's IP as a function of the ATWn command. Right now, this command does nothing, but does not return an error because I found some BBS programs try to set this to 0 so I had to at least support no error being returned. I think setting this set to 1 (ie ATW1) could enable sending the "CARRIER" and "PROTOCOL" result codes following the CONNECT message (which might include the baud rate with it). Since we don't have a CARRIER and PROTOCOL with a wireless modem, the caller's IP address could be sent instead. This method won't interfere with the X or V commands, but instead would be an addition just like Hayes intended the W command to be. We also don't have S95 (part of the selection of how the CONNECT message is displayed), so I should probably add that as well to prevent an error message from being returned.