I have set that field, and this solved the duplicate messages. I knew there had to be something I was missing but I didn't find any mention of it on the mod_sms confluence page. So this variable indicates that the message shouldn't be delivered through SIP because I am calling the send my self, correct? If I don't call send, then I assume the message would get 1 delivery, but what if I DO edit the message. If I don't call send, will the message be delivered with the edits, or do I then have to send it my self and use this variable to indicate the original should no longer be delivered? Thank you! On Thu, Jul 2, 2015 at 2:35 PM William King <william.king@quentustech.com> wrote:
If you are receiving the message over sip, and it is being delivered unchanged to another sip endpoint, then you don't need to have an action 'send' in your chatplan. If you want to keep the chatplan action, then you must set the header on the event that you are manually handling the delivery of the sms message: <action application="set" data="final_delivery=true"/>
William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.king@quentustech.com
On 7/2/15 11:13 AM, sangdrax8 wrote:
I am trying to test out mod_sms for the chatplans and it seems to be sending two messages when I call a send. Can someone tell me if there is some configuration I am doing wrong, of if I need to file a Jira bug? If I unload the mod_sms module, only one messages i sent as expected but I was looking for the chatplan functionality.
I am currently testing on Version 1.4.19 git 73f45e3, as this was the suggested branch for production usage.
my chatplan is very basic: <include> <context name="public"> <extension name="send"> <condition> <action application="send"/> </condition> </extension> </context> </include>
when I send a message I get the following in the CLI and two sip messages are sent.
2015-07-02 18:03:38.950750 [INFO] mod_sms.c:336 Processing text message 19995550008->19995550001 in context public Chatplan: 19995550001 parsing [public->send] continue=false Chatplan: 19995550001@demo Absolute Condition [send] Chatplan: 19995550001@demo Action send()
With siptrace on I can see two send events that are identical but happen less than a millisecond apart.
send 1173 bytes to tls/[192.168.0.40]:54156 at 18:03:38.965479: send 1173 bytes to tls/[192.168.0.40]:54156 at 18:03:38.965878:
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org