Issue with Twilio and SMS on 18.0 Update 5

[Luke Burns]

We just did the upgrade to 18.0 Update 5 and are having SMS issues with Twilio. I have walked through the new guide and configured everything. I am getting an error on twill and no SMS ever gets to 3CX

Errors and Warnings​

NOTIFICATION SIDNOaf3040e1576b6670a77effe3aff750d2WARNING 12300 Twilio is unable to process the Content-Type of the provided URL. Please see Twilio's <a href="https://www.twilio.com/docs/sms/accepted-mime-types"> documentation on accepted content types </a> for more information on valid Content-Types.

DESCRIPTION
Twilio is unable to process the Content-Type of the provided URL. Please see Twilio's <a href="https://www.twilio.com/docs/sms/accepted-mime-types"> documentation on accepted content types </a> for more information on valid Content-Types.

Any help would be super appreciated.

 

[Charles_3CX]

These error messages above point to an issue with the provider, not 3cx, as far as we can see. Suggest contacting Twilio support for further troubleshooting and advice.

 

[Luke Burns]

You guys should update your documentation. If chat is disabled globally then no text messages will go through. Once we enabled chat everything worked perfect.

 

[Charles_3CX]

You guys should update your documentation. If chat is disabled globally then no text messages will go through. Once we enabled chat everything worked perfect.

I think that may be a little self explanatory though, would you not agree? Sms, WhatsApp, Facebook messages are all chat messages.

 

[mybizgeek]

For the record, SMS is working for me with the new method, but I am still getting these errors in Twilio for incoming SMS only (not outgoing), even though SMS is working fine.

 

[matrix3]

I think that may be a little self explanatory though, would you not agree? Sms, WhatsApp, Facebook messages are all chat messages.

Some may think it's self explanatory, but others won't. They will associate "chat" with only the instant message feature and think of SMS and others as separate items. it would actually be great if disabling chat only disabled IM. We have clients that have asked for that before because they use Slack and don't want people in the company using 3CX IM (Human Recourses and IT both requested it).

 

[DeePhilling38]

You guys should update your documentation. If chat is disabled globally then no text messages will go through. Once we enabled chat everything worked perfect.

Yes, I definitely thought chat meant only IM!

 

[HectorMTL]

These error messages above point to an issue with the provider, not 3cx, as far as we can see. Suggest contacting Twilio support for further troubleshooting and advice.

Hi Charles, I contacted Twilio support and they told me:

Twilio receives the text message and they forward it by POST to our 3cx webhook URL.

3cx receive the text message and route it following the settings

Until now everything is working perfect, the problem is the reply from 3cx to Twilio becuase is going back to twlio with a content type that never was expected by twilio.

For this reason the both systems are working but twilio register an error every time POST a text message to 3cx.

Please, could you escalate this issue to your development team? Thank you.

 

[mybizgeek]

Just to add to this, the Twilio error log shows this error: "Invalid Content-Type: application/json; charset=utf-8 supplied"

Found this information about a fix on StackOverflow:

I too was sending a json response and getting this error. It looks like Twilio is looking for XML in TwiML format. But if you basically just return an empty "Response" element in text/xml format, that satisfies Twilio. So here is a simplified answer for anybody else that runs into this:

public ContentResult IncomingSMS(string To, string From, string Body)
{
//do stuff
//...
return Content("<Response/>", "text/xml");
}

It was working fine with the pre-Update 5 SMS config. We only started getting this Twilio error with the new SMS config since Update 5.

 

[HectorMTL]

I agreed, version Update 4 was not generating the error. I did all changes requested to migrate the SMS settings to the trunk and it started to happens. ( The SMS service is workings, the issue is the quantity of error generated on the twilio side).

 

[YiannisH_3CX]

Thank you for reporting. We are currently looking into this

 

[SBuckley]

I am getting the same error. The number was previously configured through the old SMS method. I upgraded the system and reconfigured the SMS under the SIP Trunk and deleted the old SMS configuration under the Messaging tab.
I have updated the webhook in Twilio.
Outgoing works fine. It appears that inbound on existing conversations comes through, but new SMS (not part of an ongoing conversation) do not reach us.

 

[gerrell]

I'm seeing the same. New incoming SMS messages do not show in chat. But outgoing seems fine and incoming for existing conversations seems fine.

 

[Csut12]

Seeing same, Twilio doesn't like the JSON response, wants webhook to respond with TwiML. Messages do land but generates alerts on Twilio dashboard as message failure. However we do still received our messages (inbound and outbound - just get alert in Twilio console about message failure).

When we previously wrote own webbook for Twilio messaging, responded to Twilio POST with StatusCode: 202 and no/empty body. This way didn't need to bother with any TwiML/XML and Twilio was okay with that.

 

[jeffgeno]

We're having the same issues. Errors are logged on Twilio's site, but the messages come through. However, they're not threaded properly, so they come through as separate conversation chains on the 3cx iPhone app.

 

[dbacks2k4]

Same issue. Reconfigured trunks for new SMS and removed old Messaging config. Updated webhook URL for Twilio. All messages come in but generate erorr 12300 on Twilio.

 

[N_G]

We are checking. However, please note Twilio is third party supported only. Last time Twilio made a change in their API which required us to make an update. Twilio does not support you or us at all so its a recipe for disaster.

You should really move to a supported VoIP provider such as Voxtelesys whom we are in constant contact with and who know 3CX well and are able to support you. We are constantly fine tuning settings and testing with supported providers so this is ultimately hugely beneficial to the customer.

 

[WellBeIn]

Hello @Nick Galea and Kevin,
unfortunally, Voxtelesys don't offer French numbers. (i've re-tried this morning)
Have you an operator to advise to your french comunity ?
From what i know, actually only Twilio give french numbers no ?
tks

 

[Kevin@voxtelesys]

Hi @WellBeIn, we do support French voice numbers with a couple requirements/restrictions. We currently do not support SMS/MMS on French numbers at this time.

 

[cscit]

Unfortunately, I am getting the same issue here. Errors for every text. As far as I can tell they do come through, but Twilio is firing off errors like crazy.

I would love to move to a supported provider but every single one has SMS issues except Twilio (although I didn't get very far in Bandwidth due to local numbers having a 6-month waiting list)