I'm working on configuring kannel to send smses via kannel. I'm trying to figure out how to programmatically change the sender id with each sender message i.e If the message is from customer care then on the clients handset it should read from:XYZCustomerCare if its from billing then it should read from:XYZBilling.
From the research I've done so far I've found a little configuration option known as source_addr googling it I found a rather disturbing link to a paper on sms fraud from gsma. My quesion then is how do I control the value of th senders address while sending mesdsages via kannel?
As long as your operator allows alpha numeric IDs (whose max is around 11 xters), then there is no problem. The "to" field can have "customercare" as the sender ID. The message will go through without an issue and the subscriber will receive it. Kannel doesn't have a restriction.
Related
We are getting a lost of spam /phishing e-mails where the [From] is showing our own domain (e.g. "john#foobar.com"), but the [Mail From] (return-path) in the e-mail header is showing "root#foo-574401.hostbar.com".
Question is now, which e-mail address is actually considered by the Exchange Online block list and could someone point me to the corresponding documentation of Microsoft?
In case the block-list does not consider the [Mail From] we need to setup an transport-rule to address those kind of e-mails?
Ok, found it:
See Microsoft documentation Sender filtering procedures
Sender filtering filters inbound messages by comparing a list of
blocked senders to the value of the MAIL FROM command in SMTP
connections. For more information about sender filtering and the
Sender Filter agent, see Sender filtering.
See also Sender filtering
Sender filtering compares a list of blocked senders that's maintained
by the Exchange administrator to the value of the MAIL FROM command in
SMTP connections to determine what to do with inbound email messages
from those blocked senders. Sender filtering in Exchange Server is
provided by the Sender Filter agent, and is basically unchanged from
Exchange Server 2010.
Inbound SMS messages from Twilio have some details like the from number, etc.
My app is sending out an SMS message to a group of people about an event, and expecting a reply within a short time.
The event of course has an EventId, and I need to connect the reply received to that EventId so that I update the DB with the users who have chosen to reply.
I could store the EventId with all the numbers it was sent to, and then do a lookup based on the "From Number" from Twilio's webhook POST data (the incoming messages)
Then check the time to make sure it's within the "short time" frame I am excepting.
But I am sure there has to be a simpler way?
Like embedding the EventId into the outbound SMS and then receiving it in the inbound SMS?
I have not seen any docs or examples that show this. Is anyone aware of a way to embed the EventId directly into the two-way communication?
Or is the approach I've outlined above pretty much the only thing I can do?
Twilio developer evangelist here.
The approach you describe is indeed the best way to approach this.
Joachim mentions the ability to store cookies with SMS messages, but that only applies to incoming messages and you are looking to link to the original outbound message.
Other than that, we would be relying on the third party SMS application on your users' devices to send back data with a message and that is not something that exists.
Your best bet is to look up the From number on the incoming message, check out the last message you sent to that number and decide whether this message is related to that one and update the event accordingly.
I've been using Twilio to send SMS and things work great. The only issue is that Twilio charges for both outbound and inbound messages. As such, we've been looking for other solutions.
We thought we found it with Plivo as their pricing was more favorable for SMS.
However, with Plivo, very quickly our outbound messages are being marked as spam or something and they're not being delivered.
We are sending the exact same message every day to about 5k users at a given time in the day. The message has a url in it, but it is something our users signed up for.
Two questions:
1. Why does everything work on Twilio and not on Plivo?
2. Is there a code change I can make to ensure our outbound messages sent with Plivo are not marked as spam by carriers and then stopped?
You need to contact Plivo about this. I experience this problem too. Their carrier mark our number as spammer since we are sending almost the same messages (verification). They called their carrier and our number was white-listed.
Plivo Sales engineer here. This is indeed an issue with the carrier marking your messages as spam. We can definitely help you overcome this. Could you please drop an email to ramya(at)plivo.com and we can sort this out?
You need to contact with Plivo support , there may be problem for number prefix for country like if you are using twilio you have to add +(with country prefix) but not in Plivo. It will be better to contact with Plivo support.
Thank You
I dont know how Pilvo work but usually with SMSC there is Message Queue associated sometimes with each SMPP Client and also with Mobile Station. You can't always send messages until your certain number of request are still pending. there is a specific error code that SMSC sent to its client about message queue overflow.
BADABING BADABOM! After having a look in the Plivo administration I noticed a new option under other-settings "Automatic Encoding Of Unicode Characters". As Norway uses inernational characters this is definately a setting for me, and after enabling it all SMS are delivered as expected. So remember to enable this setting.
MAKE SURE TO ENABLE THIS:
Path: Plivo admin / Messages / Settings / Other settings
Feature: Automatic Encoding Of Unicode Characters -> Enable
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
I have built an app that sends out an SMS using the twilio number(the one assigned to me) when a message is sent I receive the SID number which is inserted into the db, along with some other general information, however I do not know how to connect the received SMS SID to the sent SMS SID that tells the system that user has responded....how does someone connect the outgoing message to what is received?
UPDATE:
Hello Devin, Thanks for the response! however, this does not help me much as I might send lets say one of three different people multiple messages in an hour.
my app is a notification app...basically it is a form that a user fills out with some basic info. one of these fileds they choose is a drop down of three different people(who the message will go to) they send the message. my app then inserts the form data explained above along with the SMSID that is returned by you guys into a DB.
the user(one of the three people descibed above) that was sent the notification above responds to the message, meaning that Twilio hits my "Request URL" and I save all the information that is returned by the user...however, and where the problem actually lies is that the SMSID for that reply is not the same as the SMSID of the sent notification...therefore I have no way to connect the SMS that was sent to the user with their response. I have looked at the cookies option and that is not what I am needing...actually your documentation actually acknowledges this issue but does not offer a solution as seen here under "Application Initiated Conversations"
https://www.twilio.com/blog/2014/07/the-definitive-guide-to-sms-conversation-tracking.html
So if you know of a way around this, I would love to hear it for sure :)
Twilio evangelist here.
The SMS protocol has no concept of a "conversation". Each message sent is unique and has no knowledge of messages sent before or after it. Twilios SMS Sid is simply a unique identifier for an individual message.
The typical way to solve this is to use the To/From phone number pair as the unique identifier of an SMS conversation. When you send your first outbound message, store the To/From phone number in your database. When the user replies Twilio will tell you what number they sent the message to and from and you can use that information to look up the original outbound message in your database.
If a "user" can be involved in several different conversations at once you either need to use a unique phone number for each seperate conversation (allowing you to use the technique above), or you need to have the user include some type of conversation ID in their reply (which you can use as the unique identifier).
You can buy a pool of numbers and as each conversation "ends", recycle the number for a new conversation.
Hope that helps.