It’s strange you are getting {MEDIA} in your inbound webhook. That variable at voip.ms should be replaced with a URL that the connector will grab to get a MMS photo if exists, or should be empty. You might try removing the ;media={MEDIA} part from your webhook and see whether that changes the behavior.
edit:
I tested this some more on my voip.ms configuration and the log for a normal inbound SMS has media with an empty value, and then returns a 202 to voip.ms. In your case it’s not returning 202 so voip.ms keeps trying to send you the same messages over and over.
I guess I should have been clearer on who wanted it…sorry for the confusion. We have a bunch of interest from my users and customers in using your module who happen to use Siptrunk.com for thier trunking. I was able to get them to give us a test account that is SMS enabled that we can give you as a playground. I cant contribute code myself but I can get some direct support from one of thier engineers or potentially code because we have a bunch of users on thier stuff. (they also own flowroute and nexvortex) so we have users that use them too for rural users who have limited porting options but I can contribute some beer money for the cause
I plan to start a wiki page on the Github repo to track SIP clients and phones that work with this. If you test out the new features, let me know your results. The main thing missing with SIP messaging to the clients is queuing of messages if client is offline. I added email notification for that case. You can go back and review a message thread in UCP when the SIP client’s message history is incomplete.
Is anyone using the module with ClearlyAnywhere / Acrobits on their mobile device alongside Flowroute as their trunk provider
I have set everything up and can send and receive SMS and MMS messages – but when i send a message i get an error (initially) but then the messages do get sent out
Spoke with Clearly support about the issue and was told:
Looks like the Module used by your trunk is sending a message regarding an Index that is not recognized by the app.
You may reach out to them to have their module not send that message.
So looking at the code there should be more debugging information available on this. I have done a little digging and am curious if we can help get a better answer or some direction on this. Can you get back in touch with our support and have them push the issue to Bryan so he can poke around and perhaps get a better direction.
@hardocp for reference as you work through the support ticket with CIP - I have (previously, and just now) tested flowroute working with UCP, Sangoma Talk (mobile) and Sangoma Desktop. No errors thrown from the clients or in the FreePBX logs.
I don’t know whether this could have anything to do with it, but please confirm you have not set Flowroute to send delivery receipts to your webhook.
I am able to send messages throught voip.ms but can’t recive them this is all I got in the logs…
[2024-03-05 15:54:11] [freepbx.INFO]: Deprecated way to add Console commands for module sangomartapi, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 15:54:11] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 15:54:15] [freepbx.INFO]: Webhook (voipms) in: Array ( [provider] => voipms [to] => {TO} [from] => {FROM} [message] => {MESSAGE} [id] => {ID} [date] => {TIMESTAMP} [media] => {MEDIA} ) [] []
[2024-03-05 15:54:15] [freepbx.INFO]: Exception Webhook (voipms): file_get_contents({MEDIA}): failed to open stream: No such file or directory [] []
[2024-03-05 15:55:02] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 15:55:02] [freepbx.INFO]: Deprecated way to add Console commands for module backup, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 15:55:02] [freepbx.INFO]: Deprecated way to add Console commands for module pbxmfa, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 15:55:02] [freepbx.INFO]: Deprecated way to add Console commands for module sangomartapi, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 16:15:06] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2024-03-05 16:15:10] [freepbx.INFO]: voipms responds: HTTP 200, {"status":"success","sms":75563905} [] []
[2024-03-05 16:15:28] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
The incoming messages are still showing on the voipms SMS/MMS Message Center Information
