| Problems with long messages and dcs |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 12, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| spinnerudi New member Username: Spinnerudi Post Number: 10 Registered: 02-2009 |
Hi NowSMS Version: v2006.10.31 We use NowSMS as SMPP Server and we have problems with long messages. First problem -------------- The DCS set in the smpp protocol has no effect. Example: SMPPDEBUG.LOG: 00 00 01 00 03 00 9F 05 00 03 04 02 01 44 61 73 data coding 03 = Latin1 (iso-8859-1) SMSDEBUG.LOG: inbound message: sender=xx, recip=xx, pid=0, dcs=0, msgFlags=6, udh=050003040201, msg=88E13928... Why dsc=0 ??? Another Example: SMPPDEBUG.LOG: 00 00 01 00 01 00 9F 05 00 03 02 02 01 44 61 73 data coding 01 = IA5 SMSDEBUG.LOG: inbound message: sender=xx, recip=xx, pid=0, dcs=0, msgFlags=6, udh=050003020201, msg=88E13928... Why dsc=0 ??? Second problem -------------- Even we set dsc to 0 in the protocol and the sms text will be misread. Example: SMPPDEBUG.LOG: 00 00 01 00 00 00 9F 05 00 03 05 02 01 44 61 73 data coding 00 = SMSC Default Alphabet (7bit) SMSDEBUG.LOG: inbound message: sender=xx, recip=xx, pid=0, dcs=0, msgFlags=6, udh=050003050201, msg=88E13928... Why msg is 88E13928...? The text was "Das ist eine Testsms...". So it should be 446173206973742065696E6520..." Could you please tell me, what is the problem? Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1936 Registered: 08-2008 |
Hi, I know that older versions of NowSMS assumed that if UDH is present in the SMPP message, the text must be 7-bit packed. I didn't think that was an issue with NowSMS 2006, but it may be. Actually ... the more that I think about it, is there an actual problem? Internally, NowSMS uses GSM encoding. So if it receives a long SMS message like this, it is going to convert it to 7-bit GSM encoding. If necessary, it will convert the encoding back to 8-bit for the outbound SMSC connection. What is your outbound SMSC connection? Are you having an actual operational problem? Or are you just looking at the SMS message queue and debug logs assuming that there is a problem? -- Des NowSMS Support | |||
| spinnerudi New member Username: Spinnerudi Post Number: 11 Registered: 02-2009 |
Thanks for the answer. Yes, there is an actual problem. See the "Second problem", the sms text will be misread. The outbound SMSC Connection is a HTTP connection. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1947 Registered: 08-2008 |
That is the detail that you omitted earlier. This has nothing to do with your inbound message submission via SMPP. You would see the exact same problem if you submitted the message via the NowSMS web interface. There are two checkbox settings available when configuring an HTTP SMSC connection that apply to this issue. 1.) Send long messages without segmentation 2.) Use 7-bit binary encoding for long text messages If you use the first option, the segmented message is sent as a single long message, and it is expected that the HTTP SMSC will perform the segmentation. If you use the second option, for any messages that include UDH, NowSMS submits the message using text instead of 7-bit binary encoding. I believe that only the first of these options exists in the NowSMS version that you are running. Of course, the version you are running is 3-1/2 years old, and there are newer versions with additional features and options. If this is a purchased copy of NowSMS, please contact us for upgrade information (http://www.nowsms.com/contact.htm). If this is an evaluation copy, then please download the updated trial version from this web site. -- Des NowSMS Support | |||
