2

This specific example is using AT&T as the carrier of the receiver.

When sending SMS messages to clients via their carrier email address (1234567890@txt.att.net) from a static email address, the messages arrive on the phone from a number in the format of 1 (400) 000-244. Every time a new SMS message is sent, that number changes slightly. This causes phones, such as the iPhone, from properly threading the SMS messages that are coming from the same source email address.

Basic research shows that this has something to do with how AT&T's gateway handles turning emails into SMS messages. We've also looked at and decided that Common Short Codes (CSC) are not worth $1000 per month to purchase, so this is not an option for us.

Does anyone know of another way around this limitation in which it would be possible to force all SMS messages from the same source email to appear that way on the phone so that they are threaded correctly?

In our configuration, the emails are going out via SMTP using the PHP PEAR Mail_Mime package. We're really looking for a way we can do it on our end without the purchase of a shared or dedicated CSC.

Charles
  • 50,943
  • 13
  • 104
  • 142
Michael Irigoyen
  • 22,513
  • 17
  • 89
  • 131
  • I'm afraid I can't test this myself to see if there's a pattern, or if you can even control it. Check with AT&T themselves. In either case, you don't have to have a shortcode unless you also want to receive SMS. You can use a bulk SMS provider to send cheaply, regardless of carrier or even country: http://stackoverflow.com/questions/4590638/cheapest-way-to-send-sms-for-number-verification – Fanis Hatzidakis Jan 26 '11 at 07:06

2 Answers2

6

Use:

<10 digit phone number>@mms.att.net

Instead of 'txt.att.net'

This will solve the short code dilemma.

sgarbesi
  • 339
  • 4
  • 6
  • This renders the message a multimedia message instead of a text message, so depending on the plan and phone the recipient may be charged differently and/or the recipient might have other annoyances like having to confirm "downloading" each message. But this works well if those are not issues for that individual. – Lectrode Apr 21 '16 at 01:30
4

For your AT&T issue they use a cluster model to send out SMS using the email gateway. To over come your problem there might be a couple of solutions but it all depends on what your needs are looks like they increment the phone number by one for each new message. Not sure how you could thread these.

Zeep Mobile lets you send SMS with a shared Short Code but they tag the end of your SMS message with ads, but the service is free (limited text per month I think)

Twilio might be a good cheap alternative as they offer such services. No short code but I believe they use the same From number for your threading issue.

Using your own GSM Modem could be an option but there is some work on getting this to work properly. Also it uses a Long Code (Think telephone number) instead of a Short Code.

There are a couple of other solutions so I will update my answer soon.

UPDATE:

Phill Pafford
  • 83,471
  • 91
  • 263
  • 383
  • Twilio gives you dedicated 10-digit numbers that you can send and receive from using simple HTTP post requests. We have short codes in an early access program right now making their way toward publicly available. You can sign up on our site. – John Sheehan Jan 26 '11 at 17:38
  • @John Sheehan where can you sign up for the short code early access program? – Yahel Jan 27 '11 at 16:40
  • This is some good information and can most likely be beneficial to other people facing similar dilemmas, however we're just trying to get around AT&T's changing number without relying on a third-party services. – Michael Irigoyen Jan 27 '11 at 21:20