Skip to content
Snippets Groups Projects
  1. Jun 26, 2022
  2. Jun 25, 2022
  3. Jun 17, 2022
  4. Jun 15, 2022
  5. Jun 11, 2022
  6. Jun 08, 2022
    • Rob Swindell's avatar
      Support unlimited number/address aliases in [alias] section of ini file · 2fc0df9a
      Rob Swindell authored
      Add support for an unlimited number of dial string (e.g. phone number) aliases in the [alias] section of the read .ini file. While the AT&Z, ATDSn support for stored numbers should work fine for the same use cases, it's limited to 20 numbers (that could be easily increased) and may be less obvious to users who it works. The [alias] aliases does not use AT commands to query/store the number aliases, just .ini file edits.
      
      Re-read .ini file when ATZ command is received. This allows applying dynamic changes to the .ini file without re-running SVDM.
      
      Address some memory-leaks when reading or making changes to .ini file.
      
      Fix ATIn command results. The normal result format (from an actual modem) is:
      <text>
      <blank-line>
      OK (or 0)
      2fc0df9a
  7. Jun 07, 2022
    • Rob Swindell's avatar
      Support option modem "speaker" (WAV file playback) control via ATM1 (turn on) · 8e658998
      Rob Swindell authored
      Support optional WAV files via .ini keys:
      RingSound
      ConnectSound
      DisconnectSound
      
      ATM0 turns "speaker" (WAV playback) off (the default), ATM1 turns on.
      
      Ignore ATLn (speaker level), ATT (tone) and ATP (pulse) commands. These are
      sometimes found in init strings which we don't want to prematurely fail with
      a parse failure and "ERROR" result.
      
      Increment version number to 0.2.
      8e658998
  8. Jun 06, 2022
    • Rob Swindell's avatar
      Perform a JS garbage collection for each new request in a reused session · ed729f9c
      Rob Swindell authored
      A reused HTTP session would never (apparently) perform garbage collection.
      The evidence of this was the collection of concurrent user.dat file opens
      that would never close until the HTTP sessions were closed. Hundreds or
      even thousands of open user.dat's have been seen. After this change,
      active web server (webv4 UI) users have not caused these spikes in open
      user.dat files, at least in my testing.
      
      If no garbage collection was being performed, then likely a lot of JS
      heap was being needlessly wasted, which could eventually result in a JS
      "out of memory" error. But that's just a theory.
      
      Investigation is needed into why the js_CommonOperationCallback()'s calls to
      JS_MaybeGC() were not sufficient to actually perform garbage collection
      in this case.
      ed729f9c
    • Rob Swindell's avatar
  9. Jun 05, 2022
  10. Jun 04, 2022
  11. Jun 03, 2022
  12. Jun 02, 2022
  13. Jun 01, 2022
Loading