Unable to place FLSMS form onto Nokia 6230

[David Isaak]

I also am unable to move past this step. I am needing to be able to demonstrate FLSMS to a group of over 30 health managers from Save the Children USA global country offices in two weeks. I would appreciate anyone being able to review my attached document (with imbedded screen shots) and advise if thy see any issue that I have overlooked. Thank you

Hi David,

It looks from the screenshots like you're running FrontlineSMS 1.5.5. Unfortunately this was released rather prematurely and is quite buggy. If you download the latest release, FrontlineSMS 1.5.8, then it's likely your issues will be solved.

Alex

Hello alex, I want ot thank you for your time and effort to review my issue and provide a recommendation.

I see that my currently installed version of FLSMS indicates 1.5.5 on the Home screen as well as in the Help tab. Although I had re-installed from a 1 June download and it indicates that 1.5.8 is installing and it is reflected in the registry as 1.5.8.

I will request a new download of 1.5.8. to ensure that I am working with the latest release.

Again, thank you for your attention.

With v. 1.5.8 installed, I continue to encounter the identical conditions as described in the atached document. Perhaps, as reading in prior posts, that it might be the AT&T SIM card not allowing the form to upload. The FLSMS Message display as send and received as well as the Nokia 6230 handset acknowledging receipt of the form. Still, upon "Enter New Data" -> "There are no new forms stored on this handset."

I would really like to demo/advocate FLSMS at the upcoming conference. I am willing to make any adjustments including procuring an alternate SIM card. If so, any U.S. domestic recommendations (online order/ship)?

there have been issues with some AT&T phones having SMS send/receive disabled from mobile applications, where an identical phone that was not AT&T branded would work fine....

are you able to get hold of any other phones to try?

Hello Ben, thanks for your reply. The phone is an unbranded/unlocked device, just with a AT&T SIM inserted. The Nokia 6230 is successfully receiving SMS messages, including the SMS received generated by FLSMS: "There is a new form available for FrontLineSMS Forms: SBD_Test01".

Also, I am receiving SMS's both from FLSMS as noted in the FLSMS "Message" log, as well as non-FLSMS generated SMS's. So, SMS is working. Still, upon "Enter New Data" no forms available is displayed. Does simply receiving the FLSMS=generated text message install, and make available, the new form with in the client app? Or, does one need to do anything additional to pull in it in for use?

However, there could certainly be some firmware block. I think I either need to obain another non-AT&T SIM or grab another phone. The other phones that I have were non-working phones.

once you got the standard SMS to your client phone saying that there was a form waiting, you need to fire up the application, and then click the "GET NEW FORMS" button, which causes the phone to send a DATA SMS to frontlinesms, which frontlinesms then responds to with the form itself.

When you clicked "get new forms" on the phone, did a message appear on your frontlineSMS desktop, which was responded to?

If that did happen, but no forms come to the phone when it is "waiting for reply" then it could be that there is an issue with the phone receiving the response SMS. When the mobile application installs/starts up it will probably ask you if the application has permission to receive messages, which you MUST respond "yes" to. If you didn't, you may need to adjust the permissions, which may even require a restart?

If no message arrived at your desktop when you hit "get new forms", then the problem may be that the server phone number you entered into the mobile application wasn't in international format, so you could try that (+1 at the start of a USA number) so that it routes correctly.

Ben

Hi Ben, again, appreciate your help.I have reviewed your comments and directions and added my responses.

I have conducted tests with both the Nokia 6230, and I got a hold of a 2nd cell phone, a LG C1300i with a Cingular (albeit they are now owned by AT&T) SIM card. The C1300i initiates Java and received the FLSMS client app over its GPRS web connection. All seems to work. I also receive all notifications from the provider network both when initially opening FLSMS on both cell phones, and when sending/receiving SMS asking if I will allow permissions for network transmission. Of course, I respond “yes”.

Step 1: send form from FLSMS Desktop to cell phone. [PUSH]
Result: Desktop FLSMS “Messages” shows SMS was “delivered to cell phone client”.

“once you got [receive] the standard SMS to [on] your client phone saying that there was a form waiting...”

Step 2: “…you need to fire up the application, and then click the "GET NEW FORMS" button, which causes the phone to send a DATA SMS to frontlinesms, which frontlinesms then responds to with the form itself.” [PULL]

Result: client cell phone, after selecting “Get New Forms” asks would you like to check the server for new forms?” “yes” was selected, and warning was given that permission required….. Then message presented “Your SMS was sent, please wait for a reply.”

Step 3: “When you clicked "get new forms" on the phone, did a message appear on your frontlineSMS desktop, which was responded to?”

“If that did happen, but no forms come to the phone when it is "waiting for reply" then it could be that there is an issue with the phone receiving the response SMS. When the mobile application installs/starts up it will probably ask you if the application has permission to receive messages, which you MUST respond "yes" to.”

“If you didn't, you may need to adjust the permissions, which may even require a restart?”

Result: YES, the initial – and subsequent “firing up” of FLSMS on the client cell phone - provided a message that permission will be needed for the application to communicate with the network and that it might incur airtime costs, and asks if I want to give the application permission to allow this”. I RESPONDED “YES”.

A request was received from client cell phone as indicated by message from desktop FLSMS in “Messages” as “Received”, and then a “Sent” – then a “Delivered” message to client cell phone with the intended form name “SBD_Test01”.

On client cell phone, a SMS message is received that “There is a new form available for FrontlineSMS forms: SBD_Test01”, then correct desktop (server) phone number is listed with current date/time.

[NOTE]:“If no message arrived at your desktop when you hit "get new forms", then the problem may be that the server phone number you entered into the mobile application wasn't in international format, so you could try that (+1 at the start of a USA number) so that it routes correctly.”

Response: I have used both the international format with a +1 for both desktop and client server numbers (including cell phone number in FLSM “Contacts) and without international +1 format.

Summary. It seems both client and desktop FLSMS are sending and receiving all SMS messages, including form delivery notification from desktop. Cell phone(s) receive SMS indicating form has been delivered. Upon opening client application and selecting “Enter New Data” on cell phone, message: “There are currently no forms stored on this handset” is displayed.

Success, swapped SIM card into SAMBA modem and installed FLSM onto another PC and turned off the firewall. I think that it was the firewall. Thanks to Alex/Ben/Ken. awesome product. Ready to test and develop training modules for Health conference.

Great news - thanks for sharing, David!

Best of luck with your testing and demos, and keep us posted on how it all goes. =)

Ken

very strange - had not thought that a firewall would affect forms in that way - will let the testing team know.

Another idea is that the forms processor module was not completely activated in your first installation, and the second fresh installation didn't have that issue - I will check with Alex if that might have been the case, as we certainly want to try and avoid any other users having the same issue as you in the future!

Many thanks for your perseverance, and letting us know when you got it working!

Ben