Clickatell callback url for 2-way-SMS doesn't take url more than 255 character - clickatell

I'm integrating Clickatell with the Zoho desk. but when I create new integration with 2-way-SMS it doesn't take a URL more than 255 characters
enter image description here

Related

What is filename for SMS-sent images processed by Twilio?

When I send an SMS to my Twilio number which includes an image, there doesn't appear to be a filename associated with the image.
I'm using Twilio Studio.
Example:
Send an SMS text with image to my Twilio number
A Twilio Studio Flow pipes the {{trigger.message.MediaUrl0}} and sends an SMS text sent to my actual phone number
The URL is of the following format https://api.twilio.com/2010-04-01/Accounts/<long-GUID-1>/Messages/<long-GUID-2>/Media/<long-GUID-3>
Clicking on this URL opens a browser pointing to a translated URL https://s3-external-1.amazonaws.com/media.twiliocdn.com/<long-GUID-1>/<long-GUID-4> and showing the original image
But no filename.
I'm trying to access the filename so I can apply a naming convention to it. How is this accessed?
The URL to download the actual media is dynamically generated.
You can refer to the blog post here:
Retrieving Twilio MMS Image URLs with Node.js

Change SMS authentication text display

After integrating with the docusign API with SMS authentication, we saw that the default text entered for the subscriber when clicking on the signature link was not ideal. Can we change this text (that initial message asking the user to select a phone and click send SMS)? We were able to change the body of the email sent, but this text could not. I looked in the documentation and could not find, is it possible?
You can customize SMS Auth screen by modifying signing resource file in your Branding in DocuSign Connect.Signing Resource Doc explains how to do it, please check Pages # 18, 19 and 20.

how to get email label from email id with gmail API?

i have a problem how to get label email (promotions, updates, forums etc) with Gmail API with low cost computational.
my app used IMAP-idle for getting a new email.
a was search and get that IMAP not support label (promotions, update etc)
the other way is using Gmail API
i know i can get a list of email id by label
but that too much computational
'new id from IMAP -> search that id in every list of label (4 label)->get the label'
it's that possible to get the label of the message with one call?
thanks
In the gmail web app you can search for lables label:friends in the Gmail api you can also search for messages
GET https://www.googleapis.com/gmail/v1/users/me/messages?q="label:friends"
the message.list method will then return all the messages within that label. If you have the message id which i am not sure is the same from imap to the gmail api you then you can do a message.get which will return the label as well

Twilio cutting SMS url short

I use twilio to send sms messages but in the message I am trying to create it is a very long url and therefore won't send in 160 characters so twilio cuts the message off and url doesn't work.
If I use the automated twilio Shorten SMS the same thing happens.
I assume there is a limit to the amount of characters Twilio will send and I believe it cannot join concatenated messages in Australia from Twilio.
Edit: as of August 2019 Twilio has discontinued its URL shortening service. You should consider using a 3rd party service that allows you to set a unique base URL.
Sharing a static base-URL for a link shortener can cause unexpected carrier filtering issues with U.S. 10-digit long codes (short codes are not carrier filtered). Carriers sometimes spam filter messages by content, and the base-URLs of the links being shared appear to be one way that they categorize spam.
Twilio is working on a next-generation URL shortener that provides randomized base URLs as an add-on to a messaging service. If you are interested in this functionality contact Twilio support.
You should check to see that URL shortening is explicitly enabled in your account before attempting to send messages.
https://www.twilio.com/console/sms/settings

Markdown is not working in the Bot Framework Twilio channel

I am trying to create a simple bot that sends images and hyperlinks by SMS using Twilio (trial account).
I do get the reply from the bot , but none of the markdown is working, even simple markdown elements like text or bing
Sample code I am using to send the message through Twilio SMS channel:
public async Task<Message> Post([FromBody]Message message)
{
if(message.Text == "Hello")
{
string messageText = "![Sample Image](http://aka.ms/Fo983c)";
return message.CreateReplyMessage(messageText);
}
Am I missing something? The emulator displays the image and other markdown properly, but when I test using my android phone and text the Twilio number to connect to the bot, it delivers raw HTML and not the rich content.
Twilio developer evangelist here. As pointed our earlier SMS is text only, so markdown or any other formatting will not work.
I just tried sending a message from a bot, and while I get the image correctly on the emulator or webchat, on SMS I only get the URL of the image (i.e. http://aka.ms/Fo983c).
According to the documentation, this is the expected behavior as it states:
Not all channels can represent all markdown fields. As appropriate
channels will fallback to a reasonable approximation, for example,
bold will be represented in text messaging as bold
So I guess for images, it will always fallback to the URL of the image.
As for sending MMS, it appears right now the botframework doesn't support it. To be clear, Twilio itself does support MMS for US and Canada, but it seems Microsoft's implementation didn't take advantage of that right now.
Hope this helps you.
I did this when I was first trying out the framework. Sorry but I don't have that code anymore however I don't recall having to do anything special. I simply sent a picture from my phone to my twilio number and then in the message properties for the message received by the bot there was an attachment field with a URL pointing to the image sent from my phone. Then I used a regular web request to pull down the image.
The details for the attachment objects and content url fields are outlined here.
Because there's no way to emulate the SMS channel you'll have to publish the code live to be able to test it out.
Have fun!

Resources