Quite possibly. Grab the app_config.php file from my message in #36, above, and put it in /apps/sms, then run Advanced->Upgrade->Schema. You may also want to go ahead and put in the changes for sms_hook_common.php. I mentioned them in December, but I'll attach them here. This file goes in the same folder.
Working SMS Integration
- Thread starter Jonathan Black
- Start date
- Status
One note: You may need to adjust your chatplan settings. This is usually located in /etc/freeswitch/chatplan/default.xml. Here's what I use.
Note that I am only allowing it to send through to the external lua script (thus SMS delivery) when it's a 10-digit phone number. Anything else just attempts to deliver internally. Your experience may dictate a different need.
Note that I am only allowing it to send through to the external lua script (thus SMS delivery) when it's a 10-digit phone number. Anything else just attempts to deliver internally. Your experience may dictate a different need.
XML:
<?xml version="1.0" encoding="utf-8"?>
<include>
<context name="default">
<extension name="demo">
<condition field="to" expression="^(.*)$">
<!-- <action application="lua" data="test.lua"/> -->
<!-- <action application="reply" data="Hello, you said: ${_body}"/> -->
</condition>
</extension>
</context>
<context name="public">
<extension name="ten-digit">
<condition field="to" expression="^(\d{10}.*)$">
<action application="set" data="final_delivery=true"/>
<action application="lua" data="app.lua sms outbound"/>
</condition>
</extension>
<extension name="other">
<condition field="to" expression="^(.*)$">
<action application="set" data="final_delivery=true"/>
<action application="send"/>
</condition>
</extension>
</context>
</include>
Yes, something is definitely wrong there, and you won't see any info without those tables.
FYI, I just realized that the version of app_config.php I posted above, while correct otherwise and fine for your use in regards to table schema, doesn't contain the additional settings for carrier Telnyx as I mentioned in my original post. I'm prepping a couple of servers for a new install (FPBX 4.4/FS 1.8) and noticed that. I'm hoping to get a clean install set out of this that I can use for submission to the project.
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 with the softphone client. It is a problem with Freeswitch. And apparently, not even with the SMS module itself. This bug report indicates that it is an issue with the underlying handler. In spite of the lack of any apparent definite resolution to that bug report, we have only replicated the problem under 1.6.x versions of Freeswitch and not 1.8.x, so it looks like the problem has been fixed. I believe @MTR has also experienced similar results.
Unfortunately, our production systems are currently running 1.6.x, so we have had to disable the module while prepping a transition. There are some complicating factors that make this transition difficult, which I won't go into.
Suffice it to say that I strongly recommend that if you are considering using this module, make sure that you on Freeswitch 1.8.
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 with the softphone client. It is a problem with Freeswitch. And apparently, not even with the SMS module itself. This bug report indicates that it is an issue with the underlying handler. In spite of the lack of any apparent definite resolution to that bug report, we have only replicated the problem under 1.6.x versions of Freeswitch and not 1.8.x, so it looks like the problem has been fixed. I believe @MTR has also experienced similar results.
Unfortunately, our production systems are currently running 1.6.x, so we have had to disable the module while prepping a transition. There are some complicating factors that make this transition difficult, which I won't go into.
Suffice it to say that I strongly recommend that if you are considering using this module, make sure that you on Freeswitch 1.8.
I posted a new thread, but I guess I could have just asked in this one.
What would it take to add an additional provider? Looking to get SignalWire added in and working with SMS and maybe even MMS since they have that capability.
Any guidance would be greatly appreciated.
What would it take to add an additional provider? Looking to get SignalWire added in and working with SMS and maybe even MMS since they have that capability.
Any guidance would be greatly appreciated.
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 SignalWire requires.
In a nutshell, (and without looking at their API at all) you will probably need to add five things:
- Add a new 'if carrier = "signalwire"' section to the /apps/sms/index.lua script. This is for outbound.
- Add new "sms_hook_signalwire.php" for inbound.
- Add new settings under Advanced/Default Settings. This is so it shows up in the GUI and you can pick that carrier.
- Add the carrier's send-from IP address to the ACL. This whitelists them for you.
- Add webhook URL on SignalWire's site for https://yourdomain/app/sms/hook/sms_hook_signalwire.php.
FuncVoip, i faced the same issue. The tables are not being created. Did you solve it?
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?
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 tweaked a couple of settings in the attached. Give this a try and see how it works.
I have already tried to execute this app_config.flie version without success. It seems to be an strange underline character issue "_", isnt it?
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?
Tried to remove the "_" character but the issue still happens. It does not create the table. I am not very familiar with PHP language, maybe this an issue related with PHP version as well.
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.
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.
The issue was related to a PG database lock situation, as it is a Cluster. Thanks a lot.
- Status