iSMS

[Robert Gismondi]

Messages to folks with iPhones appear to get dropped when sent from the iSMS server using Extended Ascii 8-bit configuration. Message get through when straight ascii format is used. But, certain characters are converted to spaces using ascii. Examples are single quotes (‘) and the hat symbol (^) to name a few.

Can anyone tell me if they experienced the same? If so, is there a solution?

Thanks.

Bob

[Darrik Spaude]

Hi Robert,

Do you know if there is a specific carrier for the iPhones that don’t receive the SMS? For example, does the extended message get through to AT&T iPhone but not Verizon iPhones? Some customers of various products (not necessarily our own) are having problems with Verizon iPhones.

https://community.verizonwireless.com/thread/495728

However, if you are finding that this is a general problem (affects AT&T, Verizon, Sprint, etc. iPhones), then it would be best to start a support case.

Also, have you tried contacting Apple regarding this issue? If so, what is the radar number?

[Robert Gismondi]

Darrik,

I have narrowed it down to iPhones on Verizon’s network. AT&T phones appear to receive all messages, as Verizon phones do not.

Rather than trouble shot Verizon’s network, we have decided to send all of our text messages via ascii (not extended ascii). This insures that all of our messages get through regardless of provider.

Now, my trouble is find a way to recode certain ascii charaters that get convered to emply spaces, such as the ^ and ‘ when sending via ascii.

Do you know why the iSMS can not send these charaters to iPhones? I have tested this on different phones using different providers. These sysmbols are converted to empty spaces in each instance.

Any help is appreciated!

Thanks.

Bob

[Robert Gismondi]

Darrik,

Let me clarify something in my last post.

Messages from our iSMS using the characters ^ and ‘ are converted to empty spaces on ALL the different phones used in our tests. The problem is not limited to just iPhones.

Thanks.

Bob

[Bryon Davis]

Hi Bob,

There is sometimes a issue when sending Extended ASCII between different carriers. Many times another won’t accept Extended ASCII unless it’s across their own network.

There is a known issue with special characters not being handled correctly. We are currently working on firmware to correct this and handle more special characters. In the mean time you code try using Unicode.

Regards,

Bryon

[Robert Gismondi]

In standard ascii, we can send %28 from iSMS and receive “(” (without the quotes) on any cell phone. Most of the Hexidecimal symbols work.

Why can we not send %27 and receive “‘” (without the quotes)!

This is an urgent request!

Thanks.

Bob

[Bryon Davis]

Hi Bob,

The problem with the single quotes is also part of the known problem with special characters. We are working on a fix for this and should have something fairly soon.

Regards,

Bryon

[Author]

Posts