| Any CLUE how to Receive these characters Ü, ö, ü as an SMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I am unable to receive some Characters when sending an SMS from NowSMS web interface just receive a blank in the place of that character some of those characters are "ü", "Ü" and "ö" even though they exist in the The GSM 03.08 Default Character Set http://www.csoft.co.uk/character_sets/gsm.htm http://www.ozeki.hu/index.phtml?ow_page_number=137 What could be the problem. Using the SMPP interface | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 927 Registered: 10-2002 |
I take it this is a follow-up to: http://support.nowsms.com/discus/messages/1/894.html Are you saying that you are connecting to the service provider via SMPP (SMSC list in NowSMS includes a definition for an SMPP connection to the service provider)? When NowSMS sends over SMPP, the characters are encoded as per the GSM tables that you reference, so there should not be any problem. Let me ask you this ... are you submitting the message using our web form, or are you performing an HTTP request direct? Our web form tells the web browser to format the HTTP request using UTF-8 characters. Perhaps you are trying an HTTP request direct using standard iso-8859-1 encoding? If so, either change your request to use UTF-8 encoding, or add "&charset=iso-8859-1" to the URL that you generate. | |||
| Anonymous |
Here is the SMSDEBUG.LOG 21:38:23:750 [21] ThreadProcessConnection: Processing request /Send%20Text%20Me ssage.htm?PhoneNumber=%2Bxxxxxxxxxxxx&Text=%C3%9C+%C3%B6+%C3%BC&InfoCharCounter= &PID=&Submit=Submit 21:38:23:750 [21] Debug: 1 recipient entries 21:38:23:750 [21] Debug: +xxxxxxxxxxxx --- > Recipient of SMS 21:38:24:718 [5] ThreadProcessModem: Processing 3FCCA275.req... Here is the SMSOUT File output 2003-12-02 21:38:24,3FCCA275.req,10.1xx.xx.x,+xxxxxxxxxxxx,OK -- SMPP - SMSC1 L:8006,Text="├£ ├╢ ├╝" The text that I sent "Ü ö ü" but haven't receive the text I am using the downloadable version of nowsms v 5.0(b20031006) What could be the problem | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1303 Registered: 10-2002 |
Hi, I believe you also posted some additional information here: http://support.nowsms.com/discus/messages/1/1583.html I'm going to follow-up here, since you've posted a portion of the debug log here. The text appearing in the debug log is normal. Internally, NowSMS uses the UTF-8 character set, and the displayed text is the encoding for "Ü ö ü" in UTF-8. I see the same exact thing on my system if I submit that same message. So that part is normal. However, when NowSMS submits the message via SMPP, it converts the text from UTF-8 into either the GSM 7-bit character set, or Unicode. In this case, the smsdebug.log makes no mention of Unicode encoding being required (which is correct), and we would encode the message using the GSM 7-bit character set. If you look at the SMPPDebug.log, you should see something like this when the message is submitted to your service provider: 14:57:26:486 DumpPacket: 44 byte packet 14:57:26:486 DumpPacket: 00 00 00 2C 00 00 00 04 00 00 00 00 00 00 00 02 , 14:57:26:486 DumpPacket: 00 00 00 00 01 01 39 39 39 39 39 39 00 00 00 00 999999 14:57:26:486 DumpPacket: 00 00 00 00 00 00 05 5E 20 7C 20 7E ^ | ~ In this case, I submitted a text message with only the content: "Ü ö ü" My SMSDEBUG.LOG and SMSOUT-yyyymmdd.LOG were simliar to yours, with the UTF-8 encoding of those characters. But in the SMPPDEBUG.LOG, showing what is actually submitted to the SMS service provider, you'll see that the last 5 bytes of this packet are "5E 20 7C 20 7E". There's a table in the following discussion thread which lists the GSM 7-bit character encodings: http://support.nowsms.com/discus/messages/1/1103.html If you consult that table, you'll see that 5E is "Ü". 20 is space. 7C is "ö". 20 is space again. 7E is "ü". If you see the same thing in your SMPPDEBUG.LOG, then the message text is being encoded correctly. However, the service provider may have a problem in their system. I can recall one problem where an SMS service provider was routing SMS text messages to USA recipients via an e-mail gateway, and they couldn't handle any extended characters. So it might be a problem like that, or it might just be a bug in the service provider's SMPP receiver.} | |||
| Anonymous |
Thanks I'll check it out & let u know | |||
