I am sending SMS using Twilio API. During testing i found that it sometimes delivered message to the phone number but does not sends all the time. This is the case of DND activated numbers(Do Not Call List).
I knew this is because of Sender routing done by Twilio. When Twilio sends SMS using a number(only numeric sender-FROM), i received the message, but when it sends message using some alphanumeric sender(like DM-044138), it does not delivers the message.
Now my question is do we have any access to change this ? Can we set something that could guarantee the delivery even for the DND numbers ?
Any help would be highly appreciated.
Your problem is you are sending it to India.
Please review the following.
This feature is only available when sending messages to supported countries
As you can see from the list below India is not a supported country.
https://www.twilio.com/help/faq/sms/what-countries-does-twilio-support-alphanumeric-sender-id
Related
I have a web application that sends verification codes to users through clickatell. Nearly all users are in the US, and those work fine, but I have about 5 with international phone numbers who receive no texts.
I have a page set up to accept delivery notifications and dump them into a log file.
If I send a message to a US number, like +18161234567 I get a notification like so:
integrationName=MyIntegration&messageId=*******************&clientMessageId=&to=18161234567&from=1##########&status=DELIVERED_TO_GATEWAY&statusDesc=DELIVERED_TO_GATEWAY×tamp=1502911816000
But if I send a message to a non-US number, like +393921234567, I get no response from the clickatell server at all. It's like they don't even get the request. The phone number is the only difference between the two requests.
I have a case open with clickatell support but they have been less than insightful so far, just telling me they need a messageID or error code to investigate further, but since I get no response, I have none to give them.
Has anyone else experienced this or have any ideas I can use to troubleshoot?
We have a two-way number because that is required for sending texts in the US. However, clickatell notes on the two-way settings page that
If the country does not support two-way messaging, Clickatell will not submit the message (you will not be charged for messages that aren't successfully submitted)
I can't seem to find a list of countries that do or do not support two-way messaging. Do I need to add a separate integration without two-way messaging to support my international numbers?
UPDATE: Upon further research, my international users are in 3 countries. Italy, which does not support two-way messaging, and France and Mexico, both of which do support it. Yet none of the three are working.
FURTHER UPDATE: I have tried creating a separate integration just for Italy, since they do not support two-way messaging. I have set it up to use the clickatell automatic mobile number formatting for that country. The result is the same. No text is sent and I receive no response of any kind from the server.
Can you please check/provide response from server when you submit message with number: +393921234567.
Most likely you get validation error - that this destination number not covered by number that you bought.
Have a nice day.
Does twilio provide any test mobile numbers for different countries. I want to test whether SMS is sending successfully to some mobile number in Canada.
Is there any test mobile numbers that I can use for this purpose?
Twilio developer evangelist here.
We do not have test numbers available for you to send messages to. However, you can instrument your code such that you can find out from Twilio when you send messages that they are being delivered.
I recommend you set the StatusCallback parameter when you send messages. You set it to a URL on your server that can receive incoming webhooks and it will receive a request each time your message status changes to one of the following: queued, failed, sent, delivered, or undelivered.
That way you can be sure that your messages are sending correctly and arriving at the phones you expect them to.
Let me know if that helps at all.
I recently started using Twilio to send SMS in one of my apps. Although the twilio's dashboard shows that the SMS was send using the set alphanumeric sender id. It arrives on my phone with a different number totally. Anyone have any idea why? There's nothing about this on the Twilio website.
It turns out this is a carrier problem. They can change sender id (within reason) to increase the chance that an SMS is delivered. So there's basically nothing Twilio can do about it.
If you still have doubts, contact Twilio support.
My web app sends an SMS text message to users in the US when they enter their phone number, using the Nexmo API. When the SMS contains a link, it does not get delivered to users if their carrier is Verizon or T-Mobile. For other carriers, such as Sprint and AT&T, it does get delivered. It does not generate error messages in any case with Nexmo and I still get charged for the text even if it gets blocked by the carrier.
I contacted Nexmo and they replied:
I would say it is very likely that the link in this sms caused a spam
filter to block this message, especially if other plain content
messages have been delivered to this number successfully. So the issue
with US LVNs is that they are intended for pure P2P traffic and this
is why sending a link might be suspicious and seen as a message
originated from an application. Unfortunately there is nothing we can
do about this as it is set by the US carriers.
These are not definitely not spam or marketing messages. How can I send a link in an SMS message and not get blocked?
I had the same issue recently. All major carriers have some basic checks in place which blocks the SMS from getting delivered if you use short links (e.g.http://abc.gl/1432). The SMS will get delivered as long as you have a .com in the URL (e.g. http://abc.gl.com/1432)
Well, I observed that some carriers mark it as spam if have "Some Message. Click Here http://example/somelink" format.
Removing "Click here" part worked for me.
i.e. "Some Message. http://example/somelink"
Got the same issue. I have been using twilio to a t-mobile phone in the US.
SMS Hello Alan, your code is: 146945 for website.com is not working but
SMS Hello Alan, your code is: 146945 is working fine.
I am new to Twilio API.I have trial account and I have sent Message using Twilio Rest API successfully and received message from number i.e Message as:DM-062107 and body :- Sent from your Twilio trial Account-Hello.
Now I can't able to reply this message.can any one help me to how I can reply to this and how I know that message is received.
I have contacted to Twilio technical support for same problem and get the response. Check the reason why reply option is not enabled:
Although Twilio supports sending outbound messages internationally using toll-free numbers, your Indian number may not support sending inbound messages to US toll-free numbers. I will recommend checking with your mobile carrier to see if sending messages to US toll-free numbers is supported. If not, I will recommend using a regular US number instead of a US toll-free number and kindly retest.
Twilio Evangelist here.
So, to reply to message you just send a normal SMS from your phone to the number. The way Twilio handles this is using a 'webhook'.
If you log into your Twilio account, click on the 'Number' tab, you'll see you have a telephone number there (the same one you sent an SMS with):
Once you've clicked on the number, you'll see a screen with some other details:
Here you can configure your webhook. This is basically a URL that Twilio will send your message to. So if you configure that to point to the URL of some application you have written, you'll receive an HTTP Post or Get request (you can configure which) with the contents of the message, who it is from, etc.
You can then reply to this message with Twiml, which is just XML:
<Response>
<Message>
This is the message that is sent in reply!
</Message>
</Response>
And using this you can build up a conversation!
There are a lot of details on Twilio's website with quick starts etc. There is even a video that talks it through.
Hope this helps.