Flowroute - Inbound SMS not working for all extensions but main number

[cscit]

Hey there,

Have about 8 users up and running. Outbound SMS (Flowroute) works fine, but no one gets inbound except for the main number. Some more info below:

• I have routes configured in Messaging -> flowroute to the numbers in the +1xxxxxxxxxx format to the correct extensions.
• In the extension settings, I have enabled messaging and selected the route.
• It's working with the main number so I know the webhook, secret key and access key are correct.
• Flowroute is waiting to hear from their messaging peer because we can see the SMS messages hitting their logs.
• As far as I can tell, the inbound SMS never hit 3cx, unless it's the main number of course.
• I had a 3cx partner look at the management console and settings and as far as they can tell it is set up correctly.
• This is hosted on Azure.

I'm at a loss. I thought SMS would be working for users so I rolled out to a small pilot group, but now it is biting me in the butt, because they don't have texting. Anyone have any ideas?

 

[benlv]

I am also on Flowroute and posted a similar post (See my post) yesterday evening about our SMS not working, I tried today to send a message to our main inbound number and that text went through, however inbound SMS to direct extensions does not work. I went and tested another queue and that message was delivered without issue. So after further testing It looks like it only impacts messages with a route directly to an extension versus a queue

 

[Mayur]

from what I learn, you have to setup callback URL for each of the num.. this is what I got back from Flowroute.. not sure how to setup JSON API and how does it work.. do not see this on portal..

 

[ThomasD_3CX]

Just to be on the same page, in v18 U5, the SMS must be configured under Sip Trunks and enable the SMS under Sip Trunk configuration SMS tab - https://www.3cx.com/docs/manual/sip-trunks/ . If previously the SMS/MMS feature was configured on U4 and you have updated the 3CX System to U5, the configuration will be located under Messaging > Facebook & SMS . You will have to remove this setup and move it under Sip Trunk.

Is this the case ?

 

[Mayur]

Just to be on the same page, in v18 U5, the SMS must be configured under Sip Trunks and enable the SMS under Sip Trunk configuration SMS tab - https://www.3cx.com/docs/manual/sip-trunks/ . If previously the SMS/MMS feature was configured on U4 and you have updated the 3CX System to U5, the configuration will be located under Messaging > Facebook & SMS . You will have to remove this setup and move it under Sip Trunk.

Is this the case ?

hi Thomas
system is on U4.. each SMS created have its own URL and Flowroute portal allows one URL.. so where do you get callback URL for an account and not individual DID.. and if you have to setup per DID callback URL, where does that apply?

 

[SweetAction]

hi Thomas
system is on U4.. each SMS created have its own URL and Flowroute portal allows one URL.. so where do you get callback URL for an account and not individual DID.. and if you have to setup per DID callback URL, where does that apply?

Flowroutes pretty cool in that you can have a "default" callback URL that applies to the entire account, visible via their web portal, and you can also have a callback URL that's specific applied to a DID (can only be accessed/set/updated via API). SO if you have a specific DID that's not working with the global callback URL I would check it to see if it has a specific URL set.

You don't have to set for each DID but once you set it on a DID it's there.

 

[Mayur]

Flowroutes pretty cool in that you can have a "default" callback URL that applies to the entire account, visible via their web portal, and you can also have a callback URL that's specific applied to a DID (can only be accessed/set/updated via API). SO if you have a specific DID that's not working with the global callback URL I would check it to see if it has a specific URL set.

You don't have to set for each DID but once you set it on a DID it's there.

so do you have an example of full functional setup of JSON API for callback URL for phone num? a hosting URL/phone num/3cx generated URL for each of the num.. I understand this will be mute, when 3CX updates to new version as it will be generic call back in SIP/SMS setup?

 

[SweetAction]

so do you have an example of full functional setup of JSON API for callback URL for phone num? a hosting URL/phone num/3cx generated URL for each of the num.. I understand this will be mute, when 3CX updates to new version as it will be generic call back in SIP/SMS setup?

I'm sorry, I don't understand. Are you asking me for a step by step guide on how to change the callback URL for a specific number?

 

[Mayur]

I'm sorry, I don't understand. Are you asking me for a step by step guide on how to change the callback URL for a specific number?

if you had one! I tried to JSON API file.. seem I have an error or so is reported in browser when open using URL.. I am seeing simple info.. do multiple time for each DID.. saved it with callback_flowroute.json hosted on open access and used URL on Flowroute portal! did I missed anything?


POST /v2/numbers/PHONENUMBER/relationships/dlr_callback HTTP/1.1
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json
{


"data": {


"attributes": {


"callback_url": "CALLBACK_URL_FROM_3CX_for_DID"


}


}


}

 

[SweetAction]

The easiest way...

Login to a linux box (or use WSL on your windows machine)
Run the below code, replacing the NUMBER (1xxxxxxxxxx), access_key:secretkey, and webhook URL.

curl https://api.flowroute.com/v2/numbers/1xxxxxxxxxx/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes": {"callback_url":"https://messaging.3cx.com/v3/webhook/XXXXX-XXXXX-XXXXX-XXXXX-XXXXX/flowroute/sms/xxxxxxxxxxxx"}}}' -u access_key:secret_key

 

[Mayur]

The easiest way...

Login to a linux box (or use WSL on your windows machine)
Run the below code, replacing the NUMBER (1xxxxxxxxxx), access_key:secretkey, and webhook URL.

curl https://api.flowroute.com/v2/numbers/1xxxxxxxxxx/relationships/sms_callback -H "Content-Type: application/vnd.api+json" -X POST -d '{"data": {"attributes": {"callback_url":"https://messaging.3cx.com/v3/webhook/XXXXX-XXXXX-XXXXX-XXXXX-XXXXX/flowroute/sms/xxxxxxxxxxxx"}}}' -u access_key:secret_key

seem straight fwd.. do it for all DID with appropriate info changed? do I leave SMS/MMS/SMS DLR/MMS DLR on or off?
thanks

 

[SweetAction]

seem straight fwd.. do it for all DID with appropriate info changed? do I leave SMS/MMS/SMS DLR/MMS DLR on or off?
thanks

You only have to set the callback on a DID specifically if you don't want it to follow the global settings. But once you set it... you can never go back to "use global" according to Flowroute support a while back.

We personally use this to have some DIDs send SMS to a system not 3CX (3CX didn't always support SMS).

I don't usually turn on DLR for either SMS or MMS

 

[Mayur]

You only have to set the callback on a DID specifically if you don't want it to follow the global settings. But once you set it... you can never go back to "use global" according to Flowroute support a while back.

We personally use this to have some DIDs send SMS to a system not 3CX (3CX didn't always support SMS).

I don't usually turn on DLR for either SMS or MMS

all sorted for current version of 3CX.. when new update is out from beta, how will that impact with single callback?
again thanks for straight forward solutions.

 

[SweetAction]

all sorted for current version of 3CX.. when new update is out from beta, how will that impact with single callback?
again thanks for straight forward solutions.

You will have to change the webhook URLs to the new format. I'm sure 3CX will have a guide on migrating SMS from current relay system to the new On-PBX system published at that time.

 

[Mayur]

You will have to change the webhook URLs to the new format. I'm sure 3CX will have a guide on migrating SMS from current relay system to the new On-PBX system published at that time.

your solution made my day!