| Concatenated SMS Issue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | ||||||
| Garry Garrote New member Username: Gngarrote Post Number: 2 Registered: 05-2017 |
Hi, I have an issue with concatenated SMS. The actual envelope messages received by the card is modified. - The UDH length in the first SMS part is changed from "07" to "07" - The CPI byte "70" and the byte "00" after that was removed. What should be the correct length of the message parts and the UDH of each message? NowSMS logs: 2017-05-25 17:51:44,SAR--3e-4-1,127.0.0.1,+6590200000,OK -- PROLiNK Modem Device,SubmitUser=admin;Binary=1;PID=7F;DCS=F6;UDH=0700033E0401700001D0150621151 5B00010;Data=9E9E755005705A8A6AC57BBB2EAA682E35152C8D9004459FA2A2FB293CAC2E460DA 623F90EADB0FC4DAA89E234E8546B5CDD2F7AC2A765B2C01054AB3A44593ADA50848AAF9F77AF73F DE8E6DE52292854943179D3F88011D68D11EC74A6BA8EAA0CBFADDD31537370B10C0AD594C443A7E F2CA3E6067CBA2B3C 2017-05-25 17:52:01,SAR--3e-4-2,127.0.0.1,+6590200000,OK -- PROLiNK Modem Device,SubmitUser=admin;Binary=1;PID=7F;DCS=F6;UDH=0500033E0402;Data=5A87DBE912C F98E990C5D476F7A37BC49EB6E80B3099BAB4C760ECA740E7A834A2595AEE06531BF77139946A69A 4BE4226E3D43A26DC7F068FC4C7435E4A4BFAD56BE4DE8401173C08E8C0F2F2CA6D28CACC6723571 15592BAF6DE3A348F2C51F517B4077CD7F355F66BB747796E081DE281F6018D4CF63EA4D8CA68332 6D7A1B371B8E8B67A 2017-05-25 17:52:15,SAR--3e-4-3,127.0.0.1,+6590200000,OK -- PROLiNK Modem Device,SubmitUser=admin;Binary=1;PID=7F;DCS=F6;UDH=0500033E0403;Data=61E5F6CC1FE C6BA9E84601AAEA0FC2A0445E9D7D01A6E7D8EE570632CA0F716189DC2AC0AE092803DC89264FE3D 835B42CB9FE0E5C0EB8D0454F935857C191EACBFE459756B11DBB4F28D36EB5134F0E108112EA069 70B414C0F3AFC9B0A088639302A8CCE2B580AA826DD352B32E2497788007E71C7DBC97ED489F2E7F 67442F5AC202B466C 2017-05-25 17:52:29,SAR--3e-4-4,127.0.0.1,+6590200000,OK -- PROLiNK Modem Device,SubmitUser=admin;Binary=1;PID=7F;DCS=F6;UDH=0500033E0404;Data=320949AE08F B647C3CF20B251DB56F657C89475F8AF6E8B130220148353EFA397CB56C6AF9CCE6D964934B32C4D C84C7679F9E02FB30E70FD7B529104434D8F1D8A3 Actual Envelope received by card: 80C20000B0C2D181AD0202838106069156894500920B819E440A9156185457707FF6715052712523 238C0500033E040101D01506211515B000109E9E755005705A8A6AC57BBB2EAA682E35152C8D9004 459FA2A2FB293CAC2E460DA623F90EADB0FC4DAA89E234E8546B5CDD2F7AC2A765B2C01054AB3A44 593ADA50848AAF9F77AF73FDE8E6DE52292854943179D3F88011D68D11EC74A6BA8EAA0CBFADDD31 537370B10C0AD594C443A7EF2CA3E6067CBA2B3C5A87 80C20000B0C2D181AD0202838106069156894500920B819E400A9156185457707FF6715052712533 238C0500033E0402DBE912CF98E990C5D476F7A37BC49EB6E80B3099BAB4C760ECA740E7A834A259 5AEE06531BF77139946A69A4BE4226E3D43A26DC7F068FC4C7435E4A4BFAD56BE4DE8401173C08E8 C0F2F2CA6D28CACC672357115592BAF6DE3A348F2C51F517B4077CD7F355F66BB747796E081DE281 F6018D4CF63EA4D8CA683326D7A1B371B8E8B67A61E5 80C20000B0C2D181AD0202838106069156894500920B819E400A9156185457707FF6715052712543 238C0500033E0403F6CC1FEC6BA9E84601AAEA0FC2A0445E9D7D01A6E7D8EE570632CA0F716189DC 2AC0AE092803DC89264FE3D835B42CB9FE0E5C0EB8D0454F935857C191EACBFE459756B11DBB4F28 D36EB5134F0E108112EA06970B414C0F3AFC9B0A088639302A8CCE2B580AA826DD352B32E2497788 007E71C7DBC97ED489F2E7F67442F5AC202B466C3209 80C2000068C2D1660202838106069156894500920B58440A9156185457707FF67150527125532346 0500033E040449AE08FB647C3CF20B251DB56F657C89475F8AF6E8B130220148353EFA397CB56C6A F9CCE6D964934B32C4DC84C7679F9E02FB30E70FD7B529104434D8F1D8A3 | ||||||
| Garry Garrote New member Username: Gngarrote Post Number: 3 Registered: 05-2017 |
Correction - The UDH length in the first SMS part is changed from "07" to "05" | ||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5840 Registered: 08-2008 |
Hi Garry, What log is that from? SMSOUT, I'm guessing? The UDH in the first segment is clearly invalid as it has a length byte of 07 but more than 7 bytes of UDH. How did this message enter NowSMS? We need to understand the path...the logic flow of the message entering and exiting NowSMS. There are scenarios where NowSMS will combine and then re-segment. In this type of scenario, NowSMS, by default, would add UDH elements to the other segments if they were present in the first. Wait...I understand your "correction" now...the 70 00 is getting dropped from the first segment. Assuming the log snippet is from SMSOUT, I believe NowSMS is including it, but we need to dig deeper. Enable the SMSDEBUG.LOG. What is the type of SMSC connection? Depending on type, the raw PDU that NowSMS is sending should be visible in either SMSDEBUG.LOG or SMPPDEBUG.LOG. What do you see at that stage? -- Des NowSMS Support | ||||||
| Garry Garrote New member Username: Gngarrote Post Number: 4 Registered: 05-2017 |
Hi, Attached logs for your reference. - NowSMS Logs
- Handset/Device Log
Please help to check the cause of the issue Thanks. Regards, Garry | ||||||
| Garry Garrote New member Username: Gngarrote Post Number: 5 Registered: 05-2017 |
Hi NowSMS Support, Any idea what could be the cause of the problem? Regards, Garry | ||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5846 Registered: 08-2008 |
Hi Garry, Sorry for the delay in response. From what I can see here, the PDU that is sent out via the modem is "as expected". The first message has UDH length 07 and includes 70 00. You are segmenting the message before posting to NowSMS, and NowSMS is forwarding "as is". I can only conclude that some other software on the operator side is reassembling the message, and then resegmenting ... discarding a UDH element that it does not understand in the process. Unfortunately, that is outside of our (or your) control. You might want to try recording the UDH and putting that element first 07700000033E0401 ... very small probability that this will make a difference, but worth a try. You could also try adding the 70 00 to the UDH of all segments. I realize this is against the specification...but it would be interesting to see if the 70 00 gets removed from all segments or if it is retained. Other than that, your best option is to find an SMPP service provider that supports binary messages. -- Des NowSMS Support | ||||||
