| Problem with binary message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Mihai Radu New member Username: Trepx Post Number: 1 Registered: 06-2010 |
Hello! Sometimes when I send a binary message with UDH 027000 - SIM data download, NowSMS sends a different message: Binary=1;PID=7F;DCS=F6;UDH=0700036E02017000;Data=0083D98AB11A4C068BC160B1584D468 BD16830180C0683C160B0180C66341A8D46A3D168341A8D46A3D11884C96030182C06C3CD6233D96 C36A3198D46A3D16834066132180C0613C270B4188D4623D68CB458AD56A3D1704158900683C1603 0D90C0432C2604158900683C16030D9CD1883056145180C0683C560B81AAC2883C1823463 Could you help me decode this? What kind of message it sends? I could not replicate this error as it happens rarely. Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2230 Registered: 08-2008 |
Hi, It looks like NowSMS is determining that the message is longer than 140 binary bytes, and it needs to be segmented to be sent out over the network. So NowSMS is adding segmentation headers to the UDH. The segmentation headers look to be of an ok format. Your original UDH is 027000 where 02 is the length of the UDH ... 70 is the information element identifier that corresponds to SIM data download, and 00 is the length of this particular information element. When NowSMS segments the message, the UDH becomes 0700036E02017000. 07 is the length. 00036E0201 is the first information element (00 is the identifier, 03 is the length, then 3 bytes of data) 7000 is the second information element, just like before segmentation. The receiver should remove the segmentation headers and recombine into one long message. That said, I'm looking at ETSI GSM 03.48, and the 7000 should only be included in the UDH of the first part of the message. I need to refer this back to engineering for a fix. -- Des NowSMS Support | |||
| Mihai Radu New member Username: Trepx Post Number: 2 Registered: 06-2010 |
Thank you for your reply. When I send directly this binary message to the phone, it automatically sends an SMS to the number that he received the message from. Why is this happening? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2236 Registered: 08-2008 |
Hi, I don't know why the phone would automatically send back an SMS. We are still testing an update that handles the segmentation correctly for UDH headers from ETSI GSM 03.48/SIM data download. For most UDH segmentation issues, the specification allows the information elements to be repeated in all segments of the message. However, ETSI GSM 03.48 is clear that this particular UDH element SHALL only be present in the first message segment. I can't guarantee that this will fix the problem that you are experiencing, but reading the specification, it does appear that the way NowSMS is segmenting the message is not valid. This particular fix should be available in the next 24 to 36 hours. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2250 Registered: 08-2008 |
Hi, This has taken longer to address than anticipated. An update to NowSMS is available at http://www.nowsms.com/download/nowsms20100617.zip. If you edit SMSGW.INI, and under the [SMSGW] header add RepeatUDHAllSegments=No, this will enable logic that avoids repeating the "7000" portion of the UDH in subsequent message parts. As I noted, ETSI GSM 03.48, the SIM data download specification, states that the "7000" header in the UDH should only be present in the first segmented message. By default, NowSMS repeats all UDH elements in all segmented parts of a message, which may be causing the problem that you are experiencing. -- Des NowSMS Support | |||
| Mihai Radu New member Username: Trepx Post Number: 3 Registered: 06-2010 |
Thank you very much for your support! Regards | |||
