I am using twillio authy and I need to set my own sender id for all.
I have set code to send sms like this:
$authyApi = new \Authy\AuthyApi(env('AUTH_TOKEN_TWILLIO'));
$res = $authyApi->phoneVerificationStart($mobileWithPrefix, $countryCode, 'sms', 4);
Currently, I am getting different sender id or name for different numbers.
Twilio developer evangelist here.
In order to maximise the deliverability of messages, the Authy team works hard to pre-register alpha numeric sender IDs and numbers with networks to ensure that the messages get through fast and every time.
It is possible to change the sender ID, however that requires an agreement. If you are already in contact with the Twilio sales team you will need to bring it up with them. Otherwise you can contact the Twilio sales team and get that conversation started.
Related
We are implementing an SMS tracking feature for our app using Twilio where we will send an SMS to our customer and once they reply with Yes/No
we will take action accordingly. For normal case, where each customer has one single phone number we can easily track the replies and
take action. But if the customer use the same phone number for multiple accounts and we send multiple SMS to the same customer
(eventually in a same phone number) we are not able to track which specific SMS they have replied for.
Lets take an example,
User Tom has three accounts with us. Each of the three accounts uses the same phone number P.
Twilio SMS are tracked by a combination of From/To pair.
Assuming, we are using one Twilio proxy number as sending number which is S.
Case 1: Tom has one booking canceled for a short notice period. An SMS has been sent from S->P. When a reply is received, we can easily track the reply and take the action.
Case 2: Tom has two or more bookings canceled due to a short notice period.
For each canceled booking, an SMS has been sent from S->P. When the user replies, we are unable to detect which booking to mark the reply for.
It is not possible to know which message a person has responded to in SMS. The only way to efficiently handle this is to send messages from different numbers. So, if a user signs up with the same phone number as another user then you need to assign a new Twilio number to them. Then you can tell which user you are contacting or receiving messages from by the number.
If you send out messages about bookings on the same account at the same time, then you need to be even more granular with the number access. Each notification should assign a number to use and then when a reply comes to that number it was about that notification. Then if you need to send a second message simultaneously, you attach a different Twilio number to it. And so on for more messages.
I'm using twillio for sending sms from a rails app.
Integration was very easy, but I found a problem. When i send a message the recipient receive an sms with a different number from the one I have configured on the twillio web interface.
In my case the recipients automatically reply to my message and I need that they reply to the twillio numbers in order to process the texts.
Twillio numbers is US based while the recipient's number are from mexico.
Update: In some cases – and Mexico is one of this – due to some limitation from the provider of the country the Sender ID is translated to a local number. The only solution to this was to use a local Mexican Number and to do so I had to request for the Beta global numbers since Mexico numbers are not yet completely open.
While not completely an answer to your issue with Twilio I can add some insights. Sending SMS's via international numbers so non Mexican mobile subscriber numbers is inherently tricky. This is the case for most South America countries unfortunately.
They tend to limit who can route SMS's into the country a lot more than other countries. Therefore a lot of SMS gateway providers like Twilio instead arrange with local SMS gateways to route SMS traffic into countries like Mexico. Therefore explaining why your recipients are receiving SMS from a different originator number.
As a side note I know of a couple of international players that also operate within South America which don't have this issue. They are pretty easy to Google up :)
Our scenario is as follows:
We have a marketplace where sellers will receive multiple messages throughout the day from users.
We want to send message notifications etc via sms to sellers
We would like sellers to be able to reply to a sms message notification on their phone. We want what they text to appear as their reply on our site. Is this possible?
Say a seller checks their phone as sees that they have 5 notifications, is there a way they can reply to a specific message rather than the last one sent?
Any help would be much appreciated.
As you describe the use case, it is not possible. As you suspect, there's no way to link one inbound message to a particular outbound message. I'd suggest borrowing an idea from Twitter and including a Base-36 code in the notification. If a reply contains that code, then it's in response to that original message. For example...
Notitification: A seller is interested in your widget. LFLR
Reply: #LFLR Sorry. We are sold out of the widgets.
It will take a slight bit of effort from the sellers. But, then, they are motivated to sell. Using a Base-36 code will keep the number of characters to type under five even for a million plus messages.
I have noticed that certain SMS messages that I receive from companies come with a 'sender name'. eg. Just today I received an SMS from a number I have never used before (not im my contacts), however the senders name showed up as 'Adobe'. I get this from other companies too. eg Facebook, Google & Banking.
Is it similar to how a email server works? (you tell the server who you 'are' before you send the message) Is this the case with a carrier's cell tower?
I guess I'm wondering what the service is called and how it works? (ie. can you send 'header info' with SMS messages or is the cell tower just spoofing the message's 'sender number' and replacing it with characters?)
(hopefully this is the right place to ask this question...)
The MAP protocol (the one used for sending SMS messages among others) allow specifying either a phone number or an alphanumeric number as the sender.
AFAIK this cannot be set from your phone where the sender number will be always your public phone number but SMS Centers can allow sending such messages on other interfaces like the ones used by banks and the companies mentioned by you (usually using the SMPP or UCP protocoll).
Please note that some Telcos do not allow this kind of sender address in messages originated elsewhere but sent to their customers (or they don't allow it for everybody). They use SMS spam filters/firewalls called Home Routers for this.
Mobile communication in GSM, UMTS and LTE is governed by 3GPP.
The TP-OA field in SMS-DELIVER TPDU in an incoming SMS typically contains the number of a sender.
The network fills the TP-OA field with usually an MSISDN.
Please see 3GPP TS 23.040 Figure C.10.
But in case of a company name, TP-OA can be made alphanumeric using the Type of Number Information Element as 7-bit default alphabet
I suggest you to read 3GPP TS 24.011 and 23.040 to get an idea of how SMSes work.
However, I must point out that since a sender does not send TP-OA, it can't be easily spoofed.
You enter in the "to" number and any "from" number, and the text message will send from that phone number. Not even the major SMS gateways support this, as they require all sender IDs to be pre-approved. So does anyone know how they set it up to send from that particular phone number?
In the SMS GSM protocols, the "sender id" also called OADC (Originator Address Code) is a variable. You can put any alpha numeric string with a certain max length.
Obviously this service is abusing from this functionality which is usually used for 1) branding, 2) provide a reply path for SMS a click to call number or 3) personalizing the sender for person-to-person. For instance Facebook uses it to put session ids, Skype to either put the user id or a user mobile number to provide a reply path.