1. 14 Apr, 2021 4 commits
  2. 29 Sep, 2020 2 commits
    • Denver Gingerich's avatar
      Siskin showed us our message IDs were dupes; fixed · bfa8870e
      Denver Gingerich authored
      Naively using Blather's .reply causes us to send back a message with
      the same ID as the message we received.  This is not correct for a
      <message/> stanza, so we're fixing it here, both to make Siskin happy
      and to be compliant with the XMPP specs.  Siskin's response to this
      issue could be a bit better (an error instead of silently ignoring)
      but we were able to diagnose and fix it despite that.
      
      For simplicity we just generate a UUID to use as the reply message ID.
      bfa8870e
    • Denver Gingerich's avatar
      debug help: log outgoing messages to non-JMP users · 0a089154
      Denver Gingerich authored
      We previously did not log these messages at all (not even the text we
      sent such users) so it would be hard to see how often this sort of
      message is sent.  Now we log it, both to help see how many non-JMP
      users attempt to chat with the account bot, and to debug any issues
      that might arise with those that do (see next commit for an example).
      0a089154
  3. 30 Aug, 2020 1 commit
    • Denver Gingerich's avatar
      add new 'j' command: enable/disable inbound Jingle · 460ab996
      Denver Gingerich authored
      This command lets users switch between incoming calls going to their
      JMP SIP account (the default) and incoming calls going to Jingle.
      There are a few hacks involved to make it easier to implement (no
      actual escaping and a hard-coded SIP domain), but otherwise it's
      fairly clean.
      
      Users cannot arbitrarily edit their forwarding info.  Rather, if they
      have a custom forwarding address setup, they need to contact support
      if they want a change.  But otherwise they can freely switch back and
      forth between their JMP SIP account and Jingle.
      
      Also, this has the side-effect of now allowing users to see what their
      forwarding setting is (i.e. if they have custom forwarding setup).
      460ab996
  4. 18 Aug, 2020 1 commit
    • Denver Gingerich's avatar
      add new 'm' command: show/set CNAM for JMP number · b7260c84
      Denver Gingerich authored
      This new 'm' command allows the user to set their CNAM (outgoing
      Caller ID) in an automated fashion.  The command also lets the user
      see their current CNAM value, and whether a request to set the CNAM is
      pending or not.
      
      We were able to implement this without any new database values, since
      the carrier handles all of the state related to CNAM setting, so we
      just query the carrier's APIs as needed.
      
      However, we need additional credentials in order to do this, so we've
      added a new file 'require' here to get these.  Such credentials are
      beyond those needed for a V2 user's usual operations, so we can't just
      use those either (even if all users were on V2).
      
      The 'm' command used to be used for something else (see 2e0804f8) but
      that feature was no longer needed (see 108e94c1) so we can reuse it.
      b7260c84
  5. 17 Aug, 2020 1 commit
  6. 29 Mar, 2020 3 commits
  7. 28 Mar, 2020 1 commit
  8. 30 Apr, 2018 3 commits