Two 3CX Systems SMS to One Flowroute account

[bspottjr1]

We have SMS working on a single system, no issues.
Does anyone have a method of using the SAME Flowroute account to a 2nd system.
As per procedure - you go to add SMS on that 2nd system it provides a new URL, but then there is only 1 location for that URL in Flowroute. If its updated the 1st system will no longer work.
Anyone else run into this ?

 

[illcsales]

This manual command below should work with multiple DID, in fact I believe there is no need for the preferences step 4 in Flowroute by following below:
Our experience is that if you have used other vendors with a DID like FlowSMS we can confirm you need to run this curl script from a linux terminal as the generic webhook in Flowroute preferences does not affect the DID you used with other vendors.:
curl https://api.flowroute.com/v2/numbers/FlowrouteDID/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes":{"callback_url": "3CXWebhook"}}}' -u acesskey:apikey
Full thread below:
https://www.3cx.com/community/threads/anyone-get-sms-to-work-with-flowroute.77186/post-358656

 

[bspottjr1]

Thanx for the links and info - we will review. We have requested Flowroute enable sub accounts (new feature) and will attempt this as well. Will update the thread with what we find.

 

[bspottjr1]

So to follow up
- Using a Flowroute account and a Sub Account
- we have the Parent SMS inB & outB working.
- But the Sub account only the outB works and no inB.
- Check the SSL certs - all good
- Deleted and rebuilt the messaging profile and webhook url/and api key. same results.
- Logging into the shell and running a tail on the 3cxManagementConsole.log - we see the outB message but the inB does not even hit the server. (Lightsail Hosted).
Any thoughts out there ?

 

[cobaltit]

Yes, talk to Flowroute.

 

[illcsales]

We worked with Flowroute on this last week for each DID you must complete this step for their system to know where to send the message as I suggested in my previous post the preferences step in Flowroute can be disregarded:
curl https://api.flowroute.com/v2/numbers/FlowrouteDID/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes":{"callback_url": "3CXWebhook"}}}' -u acesskey:apikey

 

[bspottjr1]

Thanx - I have a ticket open with them currently waiting for response. Are you saying enter this in the Webhook URL field of the FR acct? and swap the text for the actual acesskey:apikey ?

 

[illcsales]

We opened a SSH session, can be any machine with internet access, replacing the appropriate parts accesskey, apikey and 3CX generated callback url highlighted in red below.
curl https://api.flowroute.com/v2/11didgitDID/FlowrouteDID/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes":{"callback_url": "3CXWebhook"}}}' -u acesskey:apikey

 

[bspottjr1]

Thanx again - executed this from a mac pro shell - as normal user and as root. Both rec'd errors
normal admin user -
-bash: curl https://api.flowroute.com/v2/numbers/FlowrouteDID/relationships/sms_callback -H: No such file or directory
as root -
{"errors":[{"detail":"Numbers not found: FlowrouteDID","id":"e003f658-0612-4c20-a467-9d02ecc217fe","status":403,"title":"Invalid Resource Action"}]}

Still pending FR response - will also provide this to them in the ticket, based on the 2nd error maybe the number is not flagged properly in their system. When I review the number in the account it is flagged OptIn for SMS. so not sure what else they may need to look at

 

[illcsales]

I got the same error at first make sure your syntax is correct, you need the " "around the 3cx webhook url generated by 3cx. only change what I listed in red.... Also make sure your using api2.1on FR

 

[bspottjr1]

On w support now - i missed changing the FR DID in the string - once that was corrected it ran no errors
still not working - currently working w FR support

 

[illcsales]

I missed that too I have edited the post to reflect good luck with FR

 

[bspottjr1]

Just to update this post - FR has reached out to their SMS carrier for the InB issue - seems there is an issue that was not caught yet

 

[bspottjr1]

Issue was addressed at the FR carrier side

 

[illcsales]

For all on this issue, I went over my notes on our case and the resolution @bspottjr1 posted above was also a part of our resolution so once you have verified you done relevant steps and possibly the curl command a ticket and trace with FR should resolve the issue.

 

[bspottjr1]

Just wanted to add here - in further testing today after the FR carrier correction.
We have added an API key to FR config for an additional DID
Using the SAME SMS config in our 3CX (not adding a second)
Added an additional Route for the 2nd DID to a different extension
Tested InB & OutB successfully - And Orig still working as well

Just in case this was a fluke - added a 3rd API for a DID in FR and a 3rd route to an 3rd extension
All Worked InB & OutB - no issues with Orig either.

Note - we did not need to add the API secret;Key any where for the these additional DIDs/extension (only added the routes in 3cx)

So with these results - I am not sure we need to run the curl update for every DID/Extension

Time will tell as we add more users

 

[illcsales]

That is most likely true if you have not used your DID with another provider as we did (FlowSMS) and if you are sole source endpoint with 3CX.
However if your are using other apps for say an MSP you will most likely still have to do the curl command as that is the mechanism FR uses to reset or specify away from sole source endpoint in preferences.

 

[bspottjr1]

Totally understand and agree with those points - just wanted to get across the point from adding these extra DIDs to the 1 SMS config as routes to/from separate extensions.
We have not seen anything process/procedure addressing how to create the additional lines passed the 1st to receive the messaging.
Definitely appreciated the curl command - saved us a lot of time with FR