| SMS Problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| lge New member Username: Lge Post Number: 2 Registered: 02-2007 |
Hi, In NOW SMS 2006 Versions Greece language and special character when send a SMS as follows problem happen. - Below - 1. Input (normalcy character) 1abcdefghijklmnopqrstuvwxyz 2abcdefghijklmnopqrstuvwxyz Αδυναμ?α ενημ?ρωση? του Ελ?γξτε τι? ρυθμ?σει? σ?νδεση? γραμματοκιβωτ?ου.,￥ ￥ 2. Output (abnormality character) 1abcdefghijklmnopqrstuvwxyz 2abcdefghijklmnopqrstuvwxyz ￥e□￥□￥□□□￥□?￥□□￥□□￥□￥□ ￥□□￥□□￥□￥□￥□￥ □￥□￥□￥□￥□ Desire to inform if more informations need. Thanks | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7003 Registered: 10-2002 |
I need to know what type of SMSC connection you are using. An SMSDEBUG.LOG that shows you submitting the message ... and that shows the message being submitted to your SMSC connection would also be helpful. (The SMSDEBUG.LOG is enabled via a checkbox option on the "serial #" page of the NowSMS configuration.) It sounds like a character set issue. If you are submitting to NowSMS via its built-in web form "Send Text Message", then the web form is designed to submit text to NowSMS using the UTF-8 character set. If you are submitting to NowSMS via a direct URL submission or your own application, then you should be aware that by default, NowSMS expects that the text parameter will contain UTF-8 encoded text. It is possible to specify an alternate character set by including "&charset=" in the URL. The code for Greek is "&charset=iso-8859-7" ... for Arabic it is "&charset=iso-8859-6". Use this "&charset=" parameter ONLY if you are submitting the text encoded with its local encoding. It is best to use the native UTF-8 support if you are working in an international environment dealing with multiple character sets. For the actual sending out via SMS ... if the text cannot be represented in the GSM character set, NowSMS converts the UTF-8 string to 16-bit Unicode for sending out over SMS. In this case, all characters, even simple characters like "a" are sent out using 16 bit representation. That's just some background information. Basically, I don't know enough about your configuration to provide any specific answer. -bn | ||||
| lge New member Username: Lge Post Number: 3 Registered: 02-2007 |
Hi, I send SMSDEBUG-LOG and SMSC CONFIG file. Thanks
| ||||
| lge New member Username: Lge Post Number: 4 Registered: 02-2007 |
Hi, I'm try to again SMSDEBUG.LOG -------------------------------------------- 09:25:46:859 [9] ThreadProcessConnection: Processing connection from 203.247.145.11... 09:25:46:875 [9] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=22110001&Text=%A5%C1%A5%E4%A5%F4%A5%ED%A5 %E1%A5%EC%3F%A5%E1+%A5%E5%A5%ED%A5%E7%A5%EC%3F%A5%F1%A5%F8%A5%F2%A5%E7%3F+%A5%F3 %A5%EF%A5%F4+%A5%C5%A5%EB%3F%A5%E3%A5%EE%A5%F3%A5%E5+%A5%F3%A5%E9%3F+%A5%F1%A5%F 4%A5%E8%A5%EC%3F%A5%F2%A5%E5%A5%E9%3F+%A5%F2%3F%A5%ED%A5%E4%A5%E5%A5%F2%A5%E7%3F +%A5%E3%A5%F1%A5%E1%A5%EC%A5%EC%A5%E1%A5%F3%A5%EF%A5%EA%A5%E9%A5%E2%A5%F8%A5%F3% 3F%A5%EF%A5%F4.%2C%A1%CD+%A1%CD%0D%0A%A5%C1%A5%E4%A5%F4%A5%ED%A5%E1%A5%EC%3F%A5% E1+%A5%E5%A5%ED%A5%E7%A5%EC%3F%A5%F1%A5%F8%A5%F2%A5%E7%3F+%A5%F3%A5%EF%A5%F4+%A5 %C5%A5%EB%3F%A5%E3%A5%EE%A5%F3%A5%E5&InfoCharCounter=&PID=&DCS=&Submit=Submit 09:25:46:875 [9] Debug: 1 recipient entries 09:25:46:875 [9] UTF8StringRequiresUnicodeEncoding: Translate to/from GSM string results in loss of data 09:25:46:875 [9] UTF8StringRequiresUnicodeEncoding: Αδυναμ?α ενημ?ρωση? του Ελ?γξτε τι? ρυθμ?σει? σ?νδεση? γραμματοκιβωτ?ου.,￥ ￥ Αδυναμ?α ενημ?ρωση? του Ελ?γξτε 09:25:46:875 [9] UTF8StringRequiresUnicodeEncoding: 짜e@짜t짜@a짜?짜% 짜Y짜ly짜@짜@ 짜Y?짜@짜횆짜횉짜@ 짜n짜짜쩔짜@짜Z짜@짜@%징l 짜e짜e짜짜m?짜@e 짜@짜 @짜- 09:25:46:875 [9] ThreadProcessConnection: SMS message must be submitted with Unicode 09:25:46:875 [9] ThreadProcessConnection: Αδυναμ?α ενημ?ρωση? του Ελ?γξτε τι? ρυθμ?σει? σ?νδεση? γραμματοκιβωτ?ου.,￥ ￥ Αδυναμ?α ενημ?ρωση? του Ελ?γξτε 09:25:46:906 [9] ThreadProcessConnection: Request processing complete --------------------------------------------- Thanks | ||||
| lge New member Username: Lge Post Number: 5 Registered: 02-2007 |
Hi, We tested comparison by NOW SMS 2005 versions and 2006 versions. Test result displays normally Greek language at NOW SMS 2005 versions, and writing of Greek language broke at NOW SMS 2006 versions. 1. Input Greek languages in "Send Text Message" of Now SMS 2005 and 2006 Send Text Message : 22116093 Text: Αδυναμ?α ενημ?ρωση? Message Type: Normal Message Class: Default 2. NOW SMS 2005 Version test results File name : 2005.cap ▶ Line 17 - No:17 Line: 5.402536 Source:123.456.789.19 Destination:123.456.789.50 Protocol:SMPP Info: SMPP Submit_sm - Short Message peer to peer, command: submit_sm, seq:350, Len:91 - Data coding: 0x08 predefined message: 0 messgae length:38 3. NOW SMS 2006 Version test results File name : 2006.cap ▶ Line 7 - No:7 Line: 3.005839 Source:123.456.789.3 Destination:123.456.789.27 Protocol:SMPP Info: SMPP Submit_sm - Short Message peer to peer, command: submit_sm, seq:142178, Len:83 - Data coding: 0x08 predefined message: 0 messgae length:30 If inform your e-mail address to me, I will send 'Ethereal Log' file ASAP | ||||
| lge New member Username: Lge Post Number: 6 Registered: 02-2007 |
Hi, In NOW SMS Greece character that break about problem solution way your fast answer wait. Above Report collected data using Ethereal program. Bye | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7045 Registered: 10-2002 |
Hi, I just tried sending the following text: Αδυναμ?α ενημ?ρωση? Using the "Send Text Message" form of NowSMS 2006. I sent it out via an SMPP connection, and I sent it out via a GSM modem connection. In both cases, my phone received the message correctly. And the message length was 38, which is correct. I do not know why you would receive a message length of 30, as that is clearly incorrect. I am also puzzled by the SMSDEBUG.LOG that shows this: 09:25:46:875 [9] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=22110001&Text=%A5%C1%A5%E4%A5%F4%A5%ED%A5 %E1%A5%EC%3F%A5%E1+%A5%E5%A5%ED%A5%E7%A5%EC%3F%A5%F1%A5%F8%A5%F2%A5%E7%3F+%A5%F3 %A5%EF%A5%F4+%A5%C5%A5%EB%3F%A5%E3%A5%EE%A5%F3%A5%E5+%A5%F3%A5%E9%3F+%A5%F1%A5%F 4%A5%E8%A5%EC%3F%A5%F2%A5%E5%A5%E9%3F+%A5%F2%3F%A5%ED%A5%E4%A5%E5%A5%F2%A5%E7%3F +%A5%E3%A5%F1%A5%E1%A5%EC%A5%EC%A5%E1%A5%F3%A5%EF%A5%EA%A5%E9%A5%E2%A5%F8%A5%F3% 3F%A5%EF%A5%F4.%2C%A1%CD+%A1%CD%0D%0A%A5%C1%A5%E4%A5%F4%A5%ED%A5%E1%A5%EC%3F%A5% E1+%A5%E5%A5%ED%A5%E7%A5%EC%3F%A5%F1%A5%F8%A5%F2%A5%E7%3F+%A5%F3%A5%EF%A5%F4+%A5 %C5%A5%EB%3F%A5%E3%A5%EE%A5%F3%A5%E5&InfoCharCounter=&PID=&DCS=&Submit=Submit I assume that you were submitting this: Αδυναμ?α ενημ?ρωση? του Ελ?γξτε τι? ρυθμ?σει? σ?νδεση? γραμματοκιβωτ?ου.,￥ ￥ Αδυναμ?α ενημ?ρωση? του Ελ?γξτε If I submit that same string, my SMSDEBUG.LOG shows this: 13:29:00:069 [11] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B18432984834&Text=%CE%91%CE%B4%CF%85%CE %BD%CE%B1%CE%BC%3F%CE%B1+%CE%B5%CE%BD%CE%B7%CE%BC%3F%CF%81%CF%89%CF%83%CE%B7%3F+ %CF%84%CE%BF%CF%85+%CE%95%CE%BB%3F%CE%B3%CE%BE%CF%84%CE%B5+%CF%84%CE%B9%3F+%CF%8 1%CF%85%CE%B8%CE%BC%3F%CF%83%CE%B5%CE%B9%3F+%CF%83%3F%CE%BD%CE%B4%CE%B5%CF%83%CE %B7%3F+%CE%B3%CF%81%CE%B1%CE%BC%CE%BC%CE%B1%CF%84%CE%BF%CE%BA%CE%B9%CE%B2%CF%89% CF%84%3F%CE%BF%CF%85.%2C%EF%BF%A5+%EF%BF%A5+%CE%91%CE%B4%CF%85%CE%BD%CE%B1%CE%BC %3F%CE%B1+%CE%B5%CE%BD%CE%B7%CE%BC%3F%CF%81%CF%89%CF%83%CE%B7%3F+%CF%84%CE%BF%CF %85+%CE%95%CE%BB%3F%CE%B3%CE%BE%CF%84%CE%B5&InfoCharCounter=&PID=&DCS=&Submit=Su bmit And in my case, the message is received correctly. This suggests to me that the problem is in the web form. The browser that is submitting the web form is not properly encoding the text as UTF-8. The correct UTF-8 URL encoding for the Greek "Α" character is %CE%91. However, in your case, it appears to be getting submitted by the web browser as %A5%C1, which is not correct for UTF-8 encoding. Have you edited the "Send Text Message.htm" form from NowSMS? Do you perhaps receive different results if you try a different web browser? We include the following directive in the <head> section of the form to tell the browser that the form is UTF-8 aware, and that the browser should post the data from the form using UTF-8: <meta http-equiv=Content-Type content="text/html; charset=utf-8"> In your case, this does not seem to be happening. The reason you are getting garbage out is because what NowSMS is receiving from the web browser is already garbage. Yet ... the text appears correctly in your log, even though the hex encoding for the text does not appear to be correct. This suggests to me that the browser is submitting the text in your local character set instead of UTF-8. Are you using the exact same web browser (on the same PC) for your tests with the 2 different versions of NowSMS? I suspect that the issue is not different versions of NowSMS handling things differently ... but different web browsers, one of which is not configured to support UTF-8. -bn | ||||
