Tried setting up the SMS to Flowroute, can send messages, and Flowroute Support says everything is fine on their end and to work with 3cx, can't seem to find anything helpful in the forms, any ideas?
Inbound messages require your system to be reachable from our messaging proxy, on the HTTPs port you have selected for your installation (common ports are 5001 or 443). Additionally, you must ensure that the defined inbound route number format is in e164 format ( eg +1 123 456 7890) within your messaging configuration, otherwise, your system will receive the message and discard it immediately.
Lastly, if you recreate the messaging service, please note that the webhook URL will change. Subsequently, you must update the webhook URL from within your provider's portal!
Customers who are using custom domain must ensure:
A valid certificate covering the installations FQDN as per common certificate validation rules. Wild cards can be used, however, wild card certificates cannot be re-used for secure SIP transport as per RFC later.
Necessary "Intermediate-Certificates" must be included in the Nginx web server certificate. Follow the guidelines of your certificate issuer. Generally, all certificate issuers rely on intermediate certificates. You can test your setup here: https://www.sslshopper.com/ssl-checker.html
Our experience is that if you have used other vendors with a DID like FlowSMS 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