Hello, answers follow: On Apr 13, 8:54 pm, "[email protected]" <[email protected]> wrote: > Hi, > > I have few questions regarding this smslib. > > 1) Is there a list of compability with newer phones? Most of the > phones listed in the compatiblity page are exactly the newest and i > have difficulty purchasing them for testing purpose from mobile shop > since they aren't in production anymore. Does anyone here have any > luck with any other phone model, please do let me know. I am kinda > looking for a cheap phone model that isn't too outdated to be found > and have to work with smslib without much issues.
Well, this list is compiled from user reports. My advise is don't go too cheap. Don't go Symbian. Don't go Motorola. If you have the money, go for a dedicated GSM modem. You can also search the group for specific model reports. > 2) (Non smslib question) I was reading somewhere that the speed of > sending sms is around 6-10 messages per minute for GSM modem. Is it > same for most phones too considering they are connecting via GSM > network? Will connecting via serial port restrict the speed even > further when receiving and sending sms (since serial port speed is in > baud)? Most phones i knew comes with usb cable for connectivity > instead, i can safely use a usb to serial adaptor for it right? Yes, 6-8 messages per minute is a GSM limit. No, the serial port will not restrict you - serial port comm is a magnitute faster than the GSM network latency. USBs are fine. Check for specific phone drivers that you may need to install in order to "see" your USB connection as a serial one. Adapters may or may not work - I don't trust them much... > 3) I was skimming through smslib examples and i figure that it > actually read from sms history instead. Can i safely assume that the > actual sms will still resided in the phone inbox after reading it? If > so, does smslib provide functionality to delete the sms after reading > it (compatible phone). How bout the outgoing sms, will it > automatically reside in the phone outbox too? My aim is to develop an > automated program that will need to have long uptime without user > intervention on the phone, having a clogged inbox/outbox on some phone > will hinder incoming sms as i know. And also Of course you can delete messages from the INBOX. And my proposal is to delete them after processing - the phone's INBOX has a specific capacity available. An outbound message (from SMSLib) *usually* is not placed in the OUTBOX. But I guess this is modem specific. > 4) Having 2 threads, one for reading and one for writing > synchronously. Both threads might be run at the same time. Will this > cause any issues to most of the compatible phones ? How do i ensure > that that the operations for sending sms is successfully executed by > the phone from smslib? No issues - SMSLib ensures for the correct concurrency of your threads. The SMSLib SEND operation returns status codes - you can check them in order to know what happened to your messages. By the way, instead of having two threads, you can use the background queue for sending and just implement the reading thread yourself. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
