| Wrong char i 2 way sms |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Morten andersen New member Username: Morten Post Number: 1 Registered: 10-2006 |
I have problems with the 2 way sms and Æ Å Ø signs, they apere as small boxes, I have read all the thread about this subject but no answer. from smsdebug 17:35:44:404 [2] ModemReceiveMessages: Decoding received message index 48 from message storage ME 17:35:44:404 [2] ModemReceiveMessages: 0791447718000180240A91545232414700006001126153934004EE329E0E 17:35:44:404 [2] ModemReceiveMessages: SMSC address len = 7 17:35:44:404 [2] ModemReceiveMessages: SMSC Address = +447781001008 17:35:44:404 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 17:35:44:404 [2] ModemReceiveMessages: Sender address len = 10 17:35:44:404 [2] ModemReceiveMessages: Sender Address = +452523 17:35:44:404 [2] ModemReceiveMessages: PID = 00 17:35:44:404 [2] ModemReceiveMessages: DCS = 00 17:35:44:404 [2] ModemReceiveMessages: Anticipated user data length = 4 17:35:44:404 [2] ModemReceiveMessages: Message = next 17:35:44:404 [2] ModemReceiveMessages: AT+CMGD=48 17:35:44:434 [5] ThreadProcessInboundSMS: Processing 453A38BB.in... 17:35:44:434 [5] GetProgramToExecute: http://www.so.dk/smsnext.asp?mobil=@@SENDER@@ 17:35:44:434 [5] GetProgramToExecute: http://www.so.dk/smsnext.asp?mobil=%2B452523 17:35:44:434 [5] ThreadProcessInboundSMS: Executing http://www.so.dk/smsnext.asp?mobil=%2B452523 17:35:44:434 [5] RetrieveURL: Retrieving http://www.sou.dk/smsnext.asp?mobil=%2B452523 17:35:44:434 [5] RetrieveURL: Looking up www.so.dk 17:35:44:454 [5] RetrieveURL: Retrieving smsnext.asp?mobil=%2B452523 17:35:44:454 [5] RetrieveURL: GET /smsnext.asp?mobil=%2B452523 HTTP/1.1 User-Agent: Now SMS/MMS Gateway v2006.03.09 Accept: */* Connection: Close Host: www.so.dk 17:35:44:574 [5] HttpResponseWait: Ok 17:35:44:574 [5] RetrieveURL: got success response 17:35:44:574 [5] RetrieveURL: text/plain; Charset=iso-8859-1 17:35:44:574 [5] ThreadProcessInboundSMS: ÆÆÆØØØÅÅÅ 17:35:44:574 [5] UTF8StringRequiresUnicodeEncoding: Translate to/from GSM string results in loss of data 17:35:44:574 [5] UTF8StringRequiresUnicodeEncoding: ÆÆÆØØØÅÅÅ 17:35:44:574 [5] UTF8StringRequiresUnicodeEncoding: é@@@- 17:35:44:574 [5] BuildSMSReply: SMS message must be submitted with Unicode 17:35:44:574 [5] BuildSMSReply: ÆÆÆØØØÅÅÅ 17:35:44:604 [2] ModemReceiveMessages: OK 17:35:45:115 [2] ThreadProcessModem: Processing 453A38BC.req... 17:35:45:115 [2] ThreadProcessModem: OUT: AT+CMGS=22 17:35:45:305 [2] ThreadProcessModem: IN: > 17:35:45:305 [2] ThreadProcessModem: OUT: 0001060A91545232414700080A0186019806180145002D 17:35:46:537 [2] ThreadProcessModem: +CMGS: 0 OK you can see the "ÆÆÆØØØÅÅÅ" is now "é@@@-" ReceiveSMSCharset = iso-8859-1 d Morten | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6725 Registered: 10-2002 |
Hi Morten, It looks like there is no logic to handle HTTP response text that is in a character set other than utf-8. So what is happening is that we are trying to interpret your response as if it were in utf-8. I've got a patch that will support the "ReceiveSMSCharset" setting and apply this to the 2-way HTTP response handling (as well as applying to the HTTP submission, as it does today) ... unfortunately, I am not in a position to be able to test it today, so I can't confirm that it functions properly. The update can be downloaded from http://www.nowsms.com/download/morten.zip. I recommend backing up EXE and DLL files from your existing NowSMS installation before updating with the EXE and DLL files in this ZIP. This way, if you encounter a new problem, you can go back to the earlier version. -bn | |||
