SMSDriver - all unicode messages are corrupted | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
Author | Message | |||
Alexander Ashkinazi Unregistered guest |
We are trying to use NowSMS software to send messages to our customers. We need to send them in Russian. Our provider is SMSDriver, which gives us SMPP interface to use (with different gateways). I tried to configure NowSMS in different ways, but with no success. I used GSMPack=Yes/No parameter. Anyway messages are arriving corrupted (unreadable characters). Please help with correct configuration. We are using NowSMS Web pages, which are included into package. SMSOUT.LOG line: 2005-09-23 18:07:01,43342823.req,127.0.0.1,+972544562604,OK -- SMPP - smpp.smsdriver.com:7000,Binary=1;DCS=8;Data=0442043504410442043E0432043E04350020 0441043E043E043104490435043D04380435 SMSDEBUG.LOG line: 18:06:59:015 [5] UTF8StringRequiresUnicodeEncoding: Translate to/from GSM string results in loss of data 18:06:59:015 [5] UTF8StringRequiresUnicodeEncoding: тестовое сообщение ---> this is russian text 18:06:59:015 [5] UTF8StringRequiresUnicodeEncoding: é@@@AèBè è2è>è5è @ ---> what is this ?? 18:06:59:015 [5] ThreadProcessConnection: SMS message must be submitted with Unicode 18:06:59:015 [5] ThreadProcessConnection: тестовое сообщение ---> this is russian text again 18:06:59:031 [5] ThreadProcessConnection: Request processing complete 18:07:00:015 [2] ThreadProcessModem: Processing 43342823.req... The above logs are where "GSMPack=Yes". By the way, if this setting is off the result is the same... What I'm doing wrong? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5041 Registered: 10-2002 |
Hi Alexander, The GSMPack setting will have no effect on Russian text. Basically, these Russian characters need to be sent in Unicode format to go out via SMS. The GSMPack setting only has to do with text sent via the GSM character set (and it usually only has to be used with servers that only support SMPP v3.3). It looks like NowSMS is correctly detecting that the message text needs to go out in Unicode format. Basically you have this text: тестовое сообщение ... and that text definitely contains characters that are outside of the GSM character set. So NowSMS decides that it needs to use Unicode format to send out the message, and it converts the characters to Unicode format, the hex of which is: 0442043504410442043E0432043E043500200441043E043E043104490435043D04380435 0442=т 0435=е 0441=с 0442=т 043E=о . . . This gets sent out with a data coding of 8, which indicates that the data is Unicode (UCS-2). I'm not aware of any alternate encodings for specifying Unicode. I can only assume that the provider in question doesn't support Unicode messages (or maybe doesn't support them to your operator, or maybe the provider needs to enable something for your account). -bn |