Special characters are wrongly coming in SMS

2,003 views
Skip to first unread message

Anoop

unread,
Jun 10, 2009, 6:12:52 AM6/10/09
to jsmpp

Hello all,

When I try to send an SMS to a real SMSC, some special
characters are
coming wrongly.
eg.
if i try to send a message '@java', the message reaches mobile as
'ijava'

In my application logs, I can see that i m sending as '@java' only.

What may be the problem here.

Thanks in advance,

Best Regards,
Anoop

Maciej Pigulski

unread,
Jun 10, 2009, 6:36:47 AM6/10/09
to jsmpp
Hello,

encoding is the problem, try to use this in your code to encode the
message before sending:

http://embeddedfreak.wordpress.com/2008/10/08/java-gsm-0338-sms-character-set-translator/

Regards,
Maciej

Ashwin Moily

unread,
Jun 10, 2009, 6:37:27 AM6/10/09
to js...@googlegroups.com
Problem is from the smsc just try to send all the characters in one go and figure out wat characters replace each other . And replace the correct characters and send it
Thats how we handle .

So incase of @ it is being replaced by i
so figure out wat characters need to be sent to get @ and replace accordingly in u r message String .

One more way to fix it is asking u r smsc operator to fix this issue .

Regards
Ashwin

Maciej Pigulski

unread,
Jun 10, 2009, 6:51:35 AM6/10/09
to jsmpp
I had the same issue and encoding conversion fixed the problem, I
guess it is not SMSC issue.

Regards,
Maciej

On 10 Cze, 12:37, Ashwin Moily <ashwinmo...@gmail.com> wrote:
> Problem is from the smsc just try to send all the characters in one go and
> figure out wat characters replace each other . And replace the correct
> characters and send it
> Thats how we handle .
>
> So incase of @ it is being replaced by i
> so figure out wat characters need to be sent to get @ and replace
> accordingly in u r message String .
>
> One more way to fix it is asking u r smsc operator to fix this issue .
>
> Regards
> Ashwin
>

Anoop

unread,
Jun 10, 2009, 2:07:44 PM6/10/09
to jsmpp
Hello,

According to ETSI GSM 03.38, '@' is included in GSM character set. It
is mentioned that no
special Unicode encoding is required for these characters.

In this case, is it really required to encode the message.
I think unicode encoding is used when we are sending multilangual
SMS..



Best Regards,
Anoop
> > > Anoop- Hide quoted text -
>
> - Show quoted text -

Maciej Pigulski

unread,
Jun 10, 2009, 2:12:04 PM6/10/09
to js...@googlegroups.com
Sure, you can encode this in Unicode (UTF-16BE) and it will work, but you will have to encode all your characters in unicode so you will lose characters per message because of more space needed for such characters. I say you can do it in GSM 03.38, I did it.

Regards,
Maciej

Anoop

unread,
Jun 17, 2009, 11:59:29 AM6/17/09
to jsmpp

I tried another way out.

i changed my application's data encoding scheme to ASCII(IA5 (CCITT T.
50)/ASCII (ANSI X3.4) in smpp.pdf) in a test code which doesn't use
JSMPP stack
Then i could see that special characters are received properly.
Earlier , the test code was also giving wrong output for special
characters when SMSC default alphabet coding scheme is used.

What may be the reason for this

Probably i could not check this with JSMPP as it didn't have an enum
value for ASCII coding.
(Alphabet ). Any reason why the other data coding schemes are ignored

Best Regards,
Anoop

On Jun 10, 11:12 pm, Maciej Pigulski <maciej.pigul...@gmail.com>
wrote:
> > > - Show quoted text -- Hide quoted text -
Reply all
Reply to author
Forward
0 new messages