Well, if you are using SMSServer, there could be differences. I'm still using v3.4.6, but I briefly looked at the SMSServer source in v3.5.1 and I think it only uses the InboundPollingThread to read messages with a predefined delay and process then sequentially in the same thread. I see that the use of InboundNotification has been commented out, so any incoming +CMTI would not have any effect. Also, the release notes for v3.5.1 indicates this bug ( http://code.google.com/p/smslib/issues/detail?id=410) as closed. I guess you should not face the issue if you are using SMSServer in v3.5.1. Delenikas can confirm if this is correct.
On Mon, Nov 14, 2011 at 5:24 PM, bwillemo <[email protected]> wrote: > Nizam, > > OK. I understand. But in this case I am using the SMSServer, not the > SMSLib. Are we supposed to modify the source of the server? > > There is not way to disable the +CMTI notification and let the > InboundPollingThread do the job? > > Thank you, BW. > > On Nov 10, 1:15 pm, Nizam <[email protected]> wrote: > > The issue is duplicate invocation of the InboundNotificationProcessor > > for the same message. This will happen whenever new messages come in > > (generating a +CMTI notification) BEFORE you are done processing the > > old messages and deleting them. I think this is already noted as a bug > > and some sort of locking mechanism is being considered. Till then, > > write your own duplicate handling logic in your > > InboundNotificationProcessor. With the current implementation, you > > should expect duplicate invocations. > > > > --Nizam > > > > On Oct 31, 1:23 pm, bwillemo <[email protected]> wrote: > > > > > > > > > > > > > > > > > T., > > > > > Sorry, it was maybe confusing to have the 2 issues in 1 post... > > > > > No, the modem is not CDMA. It's a GPRS network modem, that only use as > > > GSM SMS modem. > > > > > Forget about the delivery reports, I do get them properly. I just > > > referred to an issue in the issue tracker that said to change the > > > memory locations, that in my opinion would result to not get them > > > anymore. Leaving it on SMSR will give you the delivery reports. > > > > > The actual issue I have is the duplicate incoming SMS's. What I see > > > from the logs is that I am getting a notification that a new SMS is > > > coming in with AT+CMTI. The SMS is received properly, but then it > > > seems that the InboundPollingThread is picking up the same SMS again, > > > which results in the duplicate SMS's in the database. It doesn't > > > happen every time, but several times a day... > > > > > I was wondering if it is possible to disable the notification of new > > > messages and just let the InboundPollingThread do his work? Or is > > > there something else to do? > > > > > Thank you, > > > > > BW. > > > > > On Oct 19, 8:33 pm, "T.Delenikas" <[email protected]> wrote: > > > > > > This is probably a CDMA modem, right? > > > > > > I haven't understood very well your problem... Are you missing the > delivery > > > > reports or are you getting duplicate messages? > > -- > You received this message because you are subscribed to the Google Groups > "SMSLib Discussion 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. > > -- You received this message because you are subscribed to the Google Groups "SMSLib Discussion 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.
