| Http smsc problems |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Brian Crowley New member Username: Kwailo Post Number: 1 Registered: 12-2006 |
I'm having a particular problem while testing nowsms with chinese text and a http gateway. Basically the http smsc requires the message to be sent as url encoded utf8 format, But once i submit it to nowsms it detects that the message needs to be encoded as unicode and sends it as such. My question is can I disable the conversion "UTF8StringRequiresUnicodeEncoding" and force nowsms to send the text as is or is there somthing else i can adjust? i've set up my templates in the http smsc for text and binary which both work as expected with english but once I try chinese nowsms defaults to the binary template which i dont want. Heres some of the output from the debug log: 12:35:02:625 [7] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2BXXXXXXXX&Text=3%E3%80%81AVIcodec%EF%BC %9A%E4%BE%A6%E6%B5%8B%E5%BD%B1%E7%89%87%E6%A0%BC%E5%BC%8F%E7%9A%84%E8%BD%AF%E4%B B%B6&InfoCharCounter=&PID=&DCS=&Submit=Submit 12:35:02:625 [7] Debug: 1 recipient entries 12:35:02:625 [7] UTF8StringRequiresUnicodeEncoding: Translate to/from GSM string results in loss of data 12:35:02:625 [7] UTF8StringRequiresUnicodeEncoding: 3、AVIcodec：侦测影片格式的软件 12:35:02:625 [7] UTF8StringRequiresUnicodeEncoding: 3@AVIcodecc@o@d@e@c@ 12:35:02:625 [7] ThreadProcessConnection: SMS message must be submitted with Unicode 12:35:02:625 [7] ThreadProcessConnection: 3、AVIcodec：侦测影片格式的软件 12:35:02:625 [7] ThreadProcessConnection: Request processing complete 12:35:03:453 [7] ThreadProcessConnection: Processing connection from 192.168.0.7... 12:35:03:468 [7] ThreadProcessConnection: Request processing complete 12:35:03:468 [6] ThreadProcessModem: Processing 4580D476.req... 12:35:03:906 [6] ThreadProcessModem: GET /dotnet/MEGateway.aspx?username=XXXXXXX&password=XXXXXXX&smstype=RAWW&destinatio n=%2B60123015627&body=003330010041005600490063006F006400650063FF1A4FA66D4B5F7172 47683C5F0F76848F6F4EF6&udh= beyond this I have another question concerning nowsms and mail to sms/mms. Can nowsms detect the charset encoding in the mail message and convert the message to the correct encoding for sms/mms viewing. any input on these questions and problems would be greatly appreciated. Regards Brian | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 1 Registered: 12-2006 |
Hi Brian, Unfortunately, no, there is not a setting that would accomplish this. The underlying issue is that the actual transmission of the message over the air is going to be in 16-bit Unicode, so that is what we expect to pass to the SMSC. I discussed this issue with one of our developers, and he told me that there was a setting that was partially implemented for this, but it was not complete. I've added this item to our development issues list to see if this feature can be fully implemented. But, as this is my first post to the discussion board, I am hesitant to commit to a timeline for it to be implemented. For mail to SMS/MMS, NowSMS will look at the character set encoding in the e-mail message. For SMS, NowSMS will convert the text to UTF-8, and then evaluate whether it needs to be encoded with Unicode or whether it can use the GSM character set. For MMS, NowSMS uses the character set that was used in the e-mail message, and specifies that character set in the resulting MMS message. -- Malcolm Now Wireless Support | |||
