Hi Thanasis, I think I am going to try and explain my problem in more detail. Here is what happens: On my phone, there is the menu that deals with the mobile service operator stuff, like airtime topups, airtime transfer to a friends number e.t.c. The senario is that I initiate something from this menu such as airtime transfer to a particular number. This number is the modem running under smslib. It will get a message saying 'You have received $20 from so and so.' or something like that. Now the problem is when this message arrives, smslib reports an incomming message and calls the handler. Now, it should call the handler passing in this newly arrived message right? But it doesn't. Instead, what goes to the handler is just one of the messages that were in the modem before this new message arrived so I never get to read this new message that caused the call to the handler. This is the message that I am interested in.
Moving on, say this 'strange' message has arrived and is now lying in the modem. I can see and read it from the phone's menu. So I run ReadMessages expecting it to read all the messages in the modem but suprise, all the messages in the modem are read except this 'strange' message. It seems it never gets read although it is actually there. Here is what I do to produce this problem in my testing environment. I start ReadMessages and it lists out the messages currently in the modem then it sleeps. Then I go to the service provider menu on my modem and initiate this airtime transfer with bad parameters so that I get a message back that indicates I did something wrong and so the transfer failed and I should try again blah blah blah. This is the message that I can't read via smslib yet smslib detects it coming and calls the handler but with the wrong message (One that already exists.). By the way this 'strange' message is an actual SMS and not a flash SMS. The problem in a nutshell therefore is that smslib reads other messages but can't read this one kind of message whotsoever. Thanks alot for you time. Regards, Alex. On Jul 16, 8:16 pm, Thanasis <[email protected]> wrote: > Hi, > > Are you referring to these??? > > 11736 [SMSLib-AsyncMessageProcessor : modem.com1] DEBUG smslib - > GTW: > modem.com1: IN-DTLS: MI:137 REF:0 MAX:0 SEQ:0 > 11736 [SMSLib-AsyncMessageProcessor : modem.com1] DEBUG smslib - > GTW: > modem.com1: READ PDU: 0011FF038141F40000FF0142 > 11736 [SMSLib-AsyncMessageProcessor : modem.com1] DEBUG smslib - > GTW: > modem.com1: READ PDU: 0011FF0081000000024932 > 11736 [SMSLib-AsyncMessageProcessor : modem.com1] DEBUG smslib - > GTW: > modem.com1: CheckMpMsgList(): MAINLIST: 0 > > These are submit reports. These originate from your network every time > you send a message - its something like a delivery report, but its > triggered when your messages reaches your network (whereas the > delivery report is triggered once your messages reaches the > recipient). > > SMSLib does not process these messages - either way, there is no real > value in these messages. You can safely ignore them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib User Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/SMSLib?hl=en -~----------~----~----~----~------~----~------~--~---
