Cant send @'s (message text stops when it hits an @)

Cant send @'s (message text stops when it hits an @) SearchSearch
Author Message
Nick Luckcuck
New member
Username: Naluckcuck

Post Number: 1
Registered: 03-2006
Posted on Wednesday, March 15, 2006 - 11:55 am:   

Hi All,

Every time I send a class 1 sms (over smpp to an aql smsc) with an @ in the sms content, the message content on the mobile dosent contain the @ character and none of the message after that.

Do i have to setup the character encoding differently ? Do i need an upgrade ? please help.

Im using version 5.51 (b20040823)

Thanks :-)

--
Nick
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5652
Registered: 10-2002
Posted on Wednesday, March 15, 2006 - 11:32 pm:   

Hi Nick,

This is a character set issue. Most SMPP systems expect text to be encoded in the GSM character set. But a few expect the text to be encoded in the normal ANSI character set (iso-8859-1).

The @ symbol usually causes problems because it is a NULL in the GSM character set.

NowSMS defaults to using the GSM character set for SMPP connections.

What you want to do is go into "Advanced Settings" for the SMPP connection in NowSMS, and change the "SMSC Character Set" to "iso-8859-1", and this should resolve the problem. (Go to the "SMSC" list, highlight the SMPP connection and press "Properties", then select "Advanced Settings".)

I can't remember if this "SMSC Character Set" setting existed in the original v5.51 release or not. If you don't see this option, update to v5.51k ... a free update patch can be downloaded from http://www.nowsms.com/download/latestpatch.zip ... and in that version you will definitely see the option to which I am referring.

-bn
ashot shahbazian
Frequent Contributor
Username: Animatele

Post Number: 59
Registered: 06-2004
Posted on Thursday, March 16, 2006 - 01:54 am:   

Hi Nick!

The @ sign for GSM 7-bit charset is a common problem on many SMSC-s, but if you use 8859-1 you will not have support for some special and Greek characters.

Try experimenting: set the charset to GSM for your bind to the SMSC and try sending groups of GSM symbols to your handset, as follows:

DSP0¡P¿p
£_!1AQaq
$F"2BRbr
¥G#3CScs
èL¤4DTdt
éW%5EUeu
ùP&6FVfv
ìY'7GWgw
òS(8HXhx
ÇQ)9IYiy
LFX*:JZjz
Ø1)+;KÄkä
øÆ,<LÖlö
CRæ-=MÑmñ
Åß.>NÜnü
åÉ/?O§oà

We've found that @ is received properly if it's remapped to ¡ or some other special character, depending on the SMSC. Don't be surprised if you find other discrepancies, such as with brackets, forward and back slash or $ and ¤ signs. I'm not sure if characters can be individually remapped in NowSMS however.

Regards,
Ashot
Nick Luckcuck
New member
Username: Naluckcuck

Post Number: 2
Registered: 03-2006
Posted on Thursday, March 16, 2006 - 02:41 pm:   

That works, brilliant thanks Bryce.

Thanks for the info Ashot, i will play with other characters to see where we might run into problems in the future.

Thank you both for your time :-)

--
Nick