My U.S. web-based scheduling and address book program has the functionality to send one-way messages via SMTP to SMS. IOW: My program sends out an email - and it arrives as a text message to the cell phone address - eg: firstname.lastname@example.org (AT&T wireless).
If the message is over 160 characters, AT&T simply breaks it up into multiple messages. All of the characters arrive safe and sound - but spread out over the multiple messages. Verizon will receive only 160 characters of the message and aborts the remainder of the characters. Sprint will only receive the subject line - but none of the content. I haven't checked T-mobile yet.
The goal is to have the entire message received by any carrier - just like AT&T. We modified the program such that we tell each carrier to allow only 160 characters at a time. Now, Verizon successfully breaks the email up into multiple text messages - but, we lose around 15 characters between each succeeding message. This is better, but still not good. The lost 15 characters can have important data.
Does anybody have any suggestions? Thanks!