Search results

  1. J

    Working SMS Integration

    I believe I've figured out the settings in PHP. The pull request has been submitted. I don't know how long this will take to get accepted. If anyone wants to help test, I think you can get the code at that link, but if not, let me know. In addition to the changes I listed in post #77 above, I...
  2. J

    Working SMS Integration

    I've hit a bit of a snag with loading default settings in PHP. I can, of course, load the specific settings I'm looking for directly from SQL, but I'd rather use a library function, similar to what I've referenced in Lua (based on comments above). I'm having a bit of trouble finding them in...
  3. J

    Working SMS Integration

    On point 4. Yes, that’s the default settings that we discussed before. If you have committed all your code, I can get it from github (since I need to do a diff check there anyway). If not, feel free to send it over.
  4. J

    Working SMS Integration

    ETA: based on workload, probably next week at the earliest. I squashed some more bugs today, including the multi-line problem. I have incorporated this settings change. I do need to go back and reconcile any other changes made to this module of code since I last synced--I think someone...
  5. J

    Working SMS Integration

    I'll take a look at this. I'm beta-testing some fairly big changes to this code at the moment, so I'll see if I can replicate your situation.
  6. J

    Working SMS Integration

    Exactly! I think that will work much better. It should also clean up the code and even make it more efficient, because that one single function loads all of the default (global) and domain settings into an array. They can then be accessed as needed from the array, instead of doing a SQL...
  7. J

    Working SMS Integration

    Ok. I'm working on other parts of it, but I'll look for any updates you may make. Also, you may wish to look and see how Mark handles this idea in other parts of the code. I haven't looked, but in theory, it seems like this would be a good place for a dedicated function call for retrieving...
  8. J

    Working SMS Integration

    Hmm, good question. I didn't write that portion of the code, but looking at it, apparently the author didn't envision that and didn't build in support for it. If you want to look at it, open /apps/sms/index.lua and search for v_default_settings. Looks like those domain-level settings are...
  9. J

    change voicemail greeting for different dialplans

    I know this is very late, but this question intrigued me. It turns out that, yes, you can do this. Assuming you already have multiple greetings set up and that you are using an IVR Menu for routing the call at this stage: If the caller dials the extension directly, it will use the default...
  10. J

    Working SMS Integration

    The data table error you quoted may be a bit of a red herring, though once @yukon gets this all updated, I think the point will be moot. The original error I was addressing turned out to be not fixed by that app_config.php file change, but rather an issue on the poster's system related to BDR...
  11. J

    Re-import repository keys for BDR and pglogical apt repositories failure

    I ran into the same problem. It looks like they haven't renewed their keys. In order to get my install scripts to work, I had to change my repository line to: echo 'deb [allow-insecure=yes allow-downgrade-to-insecure=yes] http://packages.2ndquadrant.com/bdr/apt/ stretch-2ndquadrant main' >>...
  12. J

    Working SMS Integration

    Here's a follow-up: We've now rolled out upgrades on our servers to Freeswitch 1.8. While we are not seeing the crash/freeze in the Freeswitch process as mentioned previously, we are still seeing the duplicated messages (120+) when the message is sent to an invalid or unregistered extension...
  13. J

    Working SMS Integration

    Just an idea: You could go into Adminer and copy/paste that CREATE TABLE command out of the Upgrade page and execute it there to see what kind of error it gives you. And if it doesn't error and just works, well then, at least you have the table created.
  14. J

    Working SMS Integration

    It definitely needs to be "v_sms_messages" and "v_sms_destinations". And this is consistent with the naming convention used throughout FusionPBX. As to PHP version, I did have problems (unrelated to this) when I tried 7.2 . I reinstalled with 7.1 and it worked much better.
  15. J

    Working SMS Integration

    And if so, did it change the output any?
  16. J

    Working SMS Integration

    No, I don't believe so. All of the Fusion tables have similar naming convention. The issue seems to be a difference in the upgrade engine and some changes that were made in 4.4. I've incorporated those in the copy I attached today. Did you try this new version?
  17. J

    Working SMS Integration

    It looks like something is wrong in the \sms\app_config.php file. It's looking for two tables named "v", not finding them, and trying to create them. Instead, it should be looking for "v_sms_messages" and "v_sms_destinations". There may be updates to the 4.4 schema upgrade engine. I've...
  18. J

    Working SMS Integration

    When you run Advanced->Upgrade->Schema, are you getting the message that the two "v_sms_*" tables don't exist, that @FuncVOIP was getting? And then at the top, is it trying to create them?
  19. J

    Working SMS Integration

    In the very first post on this thread, look at the section where I talked about adding support for Telnyx ("How to make SMS work with Telnyx"). This is a model for how to add a new carrier. Now, obviously the specifics will vary somewhat, carrier to carrier, so you will need to look at what...
  20. J

    Working SMS Integration

    I'll just put this out there for those of you attempting to use this module: I alluded to an issue in the original post, where on some softphone clients it would duplicate the message 120+ times. It will then usually crash/freeze the freeswitch process. It turns out, this was not a problem...