Problems with square bracket '[' and ']'

Problems with square bracket '[' and ']' SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » Problems with square bracket '[' and ']' « Previous || Next »
Author Message
Charmaine Tian
Unregistered guest
Posted on Friday, June 17, 2005 - 06:01 pm:   

Our system connects to NowSMS via SMPP. It works fine except when the sms content containing square brackets.

When NowSMS receives a phone-initiated sms, it replaces '[' with two bytes, 1B 3C, before sending to our system.

When our system sends a SMPP submit packet to NowSMS, it converts '[' to some junk character (capital A with two dots on top) before sending to cell.

Does anyone know what the problem is and how I can I solve it? Thanks a lot.

--Charmaine
Anonymous
 
Posted on Saturday, July 16, 2005 - 12:52 am:   

Can anyone help me with this issue? It seems NowSMS does something weird to the square brackets in a SMS message. Thanks in advance.

--Charmaine Tian
Petr
Unregistered guest
Posted on Monday, July 18, 2005 - 10:23 am:   

It isn't bug on NowSMS side but the problem is in conversion from IA5 to GSM 03.40 char. table. See document IA5.doc
application/mswordIA5 to GSM 03.40 (Word .DOC)
IA5.doc (21.0 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4721
Registered: 10-2002
Posted on Friday, July 29, 2005 - 04:11 pm:   

Hi Charmaine,

As Petr alludes to, we use the IA5 GSM 03.40 character set.

When connecting upstream to an SMPP SMSC, we do have options for whether we use this character set, or ISO-8859-1 (Latin), which is what your application seems to expect.

And when an SMPP client connects to us, we will accept either of these character sets, based upon the data_coding value. If this value is 0, we assume the default is IA5.

However, when delivering an SMS message to a connected SMPP client, we always deliver it in the IA5 character set. And we set data_coding to 0, which indicates default.

We could explore adding a configuration option to set the default character set per client. But usually SMPP client implementations have to deal with this. The SMPP client should have an option to indicate that the default character set for the SMSC is the GSM 03.40 IA5 character set.

-bn
MoRLog
Unregistered guest
Posted on Friday, October 07, 2005 - 09:31 am:   

hi from Berlin,

i need some Informatin obout UDH cod's.

i need UDH specifications for sending 8 bit Flash-SMS. Had someone auf you a doc file shich discribe the UDH aof sending SMSRING,SMSLOGO and FLASHSMS?

hope someone can help me.

thanks
MoRLoG
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5093
Registered: 10-2002
Posted on Friday, October 07, 2005 - 07:05 pm:   

A Flash SMS is an SMS with a message class of 0. Message class is denoted in the "data coding scheme", which is defined in ETSI GSM 03.38.

The short answer is that either a DCS value of 0x10 or 0xF0 indicates that a standard 7-bit message is using message class 0.

I don't specifically know what you mean by your 8-bit reference, but I would directly you to ETSI GSM 03.38.

As this is the support forum for the Now SMS/MMS Gateway product, I have to focus my priority attention toward support for our product. So I'm afraid I can't offer much further advice.

Regarding ring tones and logos, I will simply say that there is no single standard.

There is the Nokia Smart Messaging format that you can download from the Nokia web site. That is supportedly mostly by Nokia phones only, although some other manufacturers have implemented parts of that specification. You can find details at www.forum.nokia.com.

Then there is the EMS format, which was originally defined by (Sony)Ericsson, Motorola and Siemens, and has since become more of an official standard (but still not supported by Nokia). You can find details about it at www.sonyericsson.com/developer, among other locations.

Siemens generally supports EMS, but also has a format known as SEO (and you can find a reference to its spec through a search here).

But, I would also point out that the ring tones and logos that can be sent via Nokia Smart Messaging, EMS, or SEO ... are all very primitive. For graphics, we are talking about small monochrome (black & white) graphics, which are not very interesting to view in current full colour phones. And the ring tones supported by those formats are generally monophonic.

For colour images, and more advanced ring tones, WAP Push and/or MMS and/or straight WAP download are the preferred delivery mechansims.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics