€ symbol problem with long sms text | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
Author | Message | |||
liudas New member Username: Bogiukas Post Number: 13 Registered: 08-2011 |
Hello, I tested with nowsms webpage to send € symbol and it becomes @e when receive sms. This issue valid only then if sms is long sms (concatenated) and € in the text is 153-154 chart. My assessment is that when € symbols is in the text at 153-154 place submitted sms is dividing exactly at this place (153) and € symbols is splitted in two parts as well. Thats why received sms is corresponded as @e. Is there any solution to overcome this issue? Below is text sample if You want to test: 00000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000€11111 11111111111111111 looking forward You answer, Bogas | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5651 Registered: 08-2008 |
Hi Bogas, What is the SMSC connection type? We were able to recreate this with an Android modem connection and are working on a fix. We believe this would also impact SMPP with WDP adaptation, and received SMS with 2-way commands. Wandering if you might have a different combination? -- Des NowSMS Support | |||
liudas New member Username: Bogiukas Post Number: 14 Registered: 08-2011 |
hello Des, This is on SMPP SMSC when send long text sms. Is there any way to escape this situation? Bogas | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5652 Registered: 08-2008 |
Hi Bogas, Are you using iso-8859-1 as the SMPP character set by any chance? That does complicate the encoding/decoding...especially as the SMSC needs to convert back to the GSM character set when it actually sends the message out. -- Des NowSMS Support | |||
liudas New member Username: Bogiukas Post Number: 16 Registered: 08-2011 |
Hello Des, Yes I am using as default. What kind of character set do You recommend to use? Latin, Latin-9 or IA5? Thanks for Your answer. Bogas | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5653 Registered: 08-2008 |
Hi Bogas, That is interesting. In the case of "default", we believe that we are encoding correctly. The Latin encodings are where the proper encoding is unclear. We are running more tests. It is likely that the SMSC you are connecting to is doing its own decoding, then re-encoding, which would cause this problem. But we will run more tests before jumping to this conclusion. If we are correct, this is very difficult to address. The problem is that € is represented by a 2 character combination, ESC (0x1B) followed by the letter e. If the message is segmented, ESC is the last character in part 1, and e is the first character in part 2. That appears to cause a problem for systems that decode, then re-encode, without evaluating both parts as a whole. I fear the only solution is to insert a space character before the € if this condition is detected. This is possible, but strikes me as a less than desirable hack. -- Des NowSMS Support |