| Some SMS got truncated for no reason |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 02, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| ahmed r New member Username: Ahmader Post Number: 10 Registered: 04-2004 |
Hello Guys, I have a really weird issue that I need to start a thread about to know how often this issue with others to try solving it all together, and thanks in advance for whom ever read and replay to us. First let me tell you where I use NowSMS in my scenario, I have NowSMS 5.5 running into 3 different locations and connected to 3 different SMSC operators. For Arabic messages I am receiving the long text messages in three different ways and for the past year we ware trying to find out any logical case to trace that error but with no luck, I know by know everyone want to know the three different ways, here you go 1- a long SMS with more than 70 char that being received into part (1-5, 2-5, 3-5, 4-5, 5-5) and then the message get concatenated with no problem and that is the perfect scenario for everybody. 2- a long SMS with more than 70 char that being received into part (1-4, 2-4, 4-4) and as you noticed the part 3 is missing so the other three parts keep waiting into the SMS-IN folder as SAR files and never get processed. (Which we solved by collecting these messages after 10-20 minutes if the missing part(s) are not received. 3- A long SMS with more than 70 char that being received into small SMS messages with different IDs and different files with no relation to each other which is causing us big trouble to concatenate the parts into one long message by any trick, as they also sometimes deliver in sort, I mean the first part (as individual SMS) then the next part and so on, and sometimes we receive the second part then the first or the third, which I mean not sorted. Ok lets talk more advanced, we have said before it’s a mobile issue, operator or the content it self. But (and here is the funny part) the same mobile number and device and message we have send it to the same SMSC and we got it in the three scenario, and again I know most of your questions, and yes most of your question are correct like: • Maybe the SMSC operator is having multiple SMSC, and we have requested the SMSC operator to route us to one SMSC only to trace and the same problem. • We check the SMSC logs and the message are being sent to us as concatenated message although we are still receiving the 3 scenarios. • The SMS is executing the NowSMS limit, which I don’t see any limitation over NowSMS, and some times two parts of message are being truncated. Any replay will be appreciated even if not a solution maybe we can come up together to know it. Thanks and please also tell me if you need more information or you have more questions. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5785 Registered: 10-2002 |
Hi, Issue #3 might be a problem with a particular device. At least that would be what I would suspect ... that maybe a particular sending device is not actually segmenting long messages, and sending them as separate text messages. I'd try to track down a sender whose messages exhibit this problem, and see if it is consistent. I'm quite confident that if NowSMS sees them as separate messages, then the concatenation headers are not present in the messages being delivered to NowSMS. With issue #2, it maybe that the operator SMSC is sending messages faster than the modem will accept them. Experimenting with different "SMS Message Storage" settings like "Direct to Modem" may make a difference here. Also, trying different settings for "SMS Access" with "GPRS" or "GSM" may make a difference. We did make changes in the NowSMS 2006 release, where we will now only wait 30 minutes for all segments of a message to be received. If all segments are not received, we'll go ahead and process it with a missing segment after 30 minutes have passed. (Previous NowSMS versions would wait indefinitely.) But that doesn't really address the issue of why segments are missing. I'd suspect that maybe there is some handshake problem between the operator SMSC and the modem which is causing the SMSC or modem to drop messages. That's why I'd suggest different trying different settings to see if it makes a difference. -bn | |||
| ahmed r New member Username: Ahmader Post Number: 11 Registered: 04-2004 |
Hello Bryce, Sorry to disappoint you about issue #3 we have confirmed that the same mobile device can deliver the three scenarios, and we are very confident that it is not a device problem or a sender number or message content. The operator keep confirming that he sent the message to our SMPP connection with a prober header as a long text message but we are receiving them into separate messages, then the concatenation headers are not present. But in operator side it is! #2 wow of the change of 2006 and i would like to ask what to you fill in the missing part (some text is missing) and is it fixed or we can change it! cause as of now we add something we did the same trick but in interval of 10 minutes only cause we noticed that most of the operator as we are working on P-SMS expire our messages within 10 minutes period. so as you said we collect the messages and replace the missing part with some Arabic text, cause again all our SMS services are SMS>2>TV. and kindly be more clear about (trying different settings for "SMS Access" with "GPRS" or "GSM" may make a difference) do you think its a TON/NPI problem cause the operator keep saying that they see in there side all our TON/NPI values are sent as 0 only, and the funny thing again when we change the values it seems it effect the connection i mean the international number format or national number format are being processed as per the NPI/TON values but again the operator say we are sending 0, and one of the three operator we could not connect to them at all as they are restricting the TON/NPI values and they accepted to un-restrict these values only for our SMPP connection as we have a high traffic profile in that country so they wanted us to get connected to drive more traffic for them. i know some other client whom connected to the same SMSC with different SMPP client and they never faced that problem i mean #3 only but #2 its common for everybody as we deal with pre-paid mobiles and postpaid and sometimes the operator restrict there mobile customers to send more than X number of message @ the time so couple of the segment not been delivered as the certain customer queue is full so it got rejected but the other segment are already received by our modem. Thanks BN for your time and hopefully we can solve this issue after the long time we tried to figure it our from our side or try fixing it by different method but we have not luck  Regards, Ahmader | |||
| ahmed r New member Username: Ahmader Post Number: 12 Registered: 04-2004 |
Any update Bryce!  | |||
| ahmed r New member Username: Ahmader Post Number: 15 Registered: 04-2004 |
is this subject close ?  | |||
| ahmed r New member Username: Ahmader Post Number: 16 Registered: 04-2004 |
Bryce, I have some extra trace which ensure you that NowSMS is not reading the SAR properly. I haved asked one of the SMSC operators to send us a test of 10 SMS with 5 seqments, with valid SAR header but NowSMS did not read them and we received them as 50 SMS and not 10 Long SMS. Please Bryce tell me where to send these logs we really need to fix this. BTW: all my post was about DCS=8 and not DCS=0. Thanks and have a nice day. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5808 Registered: 10-2002 |
Ahmed, Logs would definitely help. If you can enable the debug log and send SMSDEBUG.LOG and SMPPDEBUG.LOG files with supposed long SMS that are not being correctly re-assembled, that would be the most helpful. Send them to nowsms@now.co.uk with "Attention Bryce" in the subject line. -bn | |||
| ahmed r New member Username: Ahmader Post Number: 17 Registered: 04-2004 |
Ok Bryce, I am sending you the Logs with same subject of this Post. Please keep in mind the Logs i am sending is not the SMPP debug or SMS debug i am sending you the TCP sniffing as CAB files, please let me know if you can not read them properly. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5814 Registered: 10-2002 |
Hi Ahmed, I've looked at your logs. I need to know specifically what version of NowSMS you are running. If it is a version prior to v5.51b, then that is the problem. Versions prior to v5.51b do not understand SMPP TLV parameters for segmentation in received messages. Earlier versions only understand segmentation headers if they are received as UDH (user data header). If you are running v5.51 or v5.51a, you can update with http://www.nowsms.com/download/latestpatch.zip. If you are running a version prior to v5.51, then you can download v5.51b as http://www.nowsms.com/download/latestinstall.exe. -bn | |||
| ahmed r New member Username: Ahmader Post Number: 18 Registered: 04-2004 |
Bryce, Oh god..... you know what i have been using NowSMS 5.50 on all the platforms i have, and i have updated to version 5.51b as you mentioned above, but i have received some error i will tell you about it little later cause i am still trying to fix it. and no need to bother you untill i confirm my settings. but in other platform i did not get this error and i try to use the TLV option but the same problem occrus so i update to NowSMS 5.51K and with out using this TLV option... and now i am getting all messages in good shape so Thanks for you and all NowSMS updates. if someone have the same problem you can just tell him to update to 5.51K and all will be fine i am going to party now over this subject and tomorrow i will try the error i got in the other platform.....hola cheeeeers -Ahmader | |||
| deadman New member Username: Deadman Post Number: 1 Registered: 05-2006 |
hi can i use nowsms to make my gcm device as a virtual SMSC? its really needed. pls | |||
