[Bryon Davis]

Hi Gustavo,
There isn’t a way to reboot the iSMS through the API. You can reboot it using telnet though. If you telnet to port 2222, login with admin username and password, and enter the command “reboot” (without the quotes) it will reboot the iSMS.

I will add a feature request for rebooting the iSMS with an API command.

Regards,
Bryon

[Bryon Davis]

Hi Harry,
Does rebooting the iSMS clear the condition?

How long does a SIM last before it fails?

Regards,
Bryon

[Bryon Davis]

Hi Gustavo,
Check if the modems are active in SMS Statistics, which is in the Statistics & Logs menu. If no modem is active, then messages won’t show up in the Outbox.

Try rebooting the unit, sometimes that will clear certain conditions were the modem is having trouble connecting to the network.

This would be much easier to troubleshoot if you made a case in the support portal at support.multitech.com.

Regards,
Bryon

[Bryon Davis]

Hi Gustavo,
Currently the receive API will only deliver new “unread” messages. There is a feature request for adding support for reading unread messages, so it may be added to a future release.

Regards,
Bryon

[Bryon Davis]

Hi Steven,
Sorry for the delay in response. There hasn’t been any new support added for MMS yet.

Regards,
Bryon

[Bryon Davis]

Hi Chad,
Sorry, there isn’t a way to query existing address book entries through the API.

Regards,
Bryon

[Bryon Davis]

Hi Chad,
Sorry, the only way to save to flash is through the web interface.

Currently you can only view unread received messages through the API. We do have a feature request for this, so it may be added to a future release.

Regards,
Bryon

[Bryon Davis]

Hi Kamran,
I’m not familiar with Delphi, but it appears that you’re trying to construct the response data, rather than the GET request for the data.

You should be using recvmsg and querycount requests in Polling mode. In Polling mode the iSMS will only deliver received sms messages when requested with a recvmsg request. The querycount request will retrieve the number of entries that are available to retrieve with the recvmsg request.

An example of a basic recvmsg request would be:

http://192.168.2.1:81/recvmsg?user=admin&passwd=admin

As a test, you could enter this in a web browser’s address bar and retrieve messages. You would need to change the IP address to match your iSMS, the port ( :81 ) to match the port set in HTTP API Configuration, and the password.

Below is more information on the recvmsg request. The parameters in [] are optional and can be used to limit which messages are retrieved.

GET /recvmsg?user=admin&passwd=admin[&count=][&from][&fdate=][&tdate=][&ftime=][&ttime=][&text=]
Query options are only used with the recvmsg? Command:
● All options given within [] indicate that they are optional
● count – number of messages to be displayed
● If filter is not given, it gives count of ALL unread messages
● from – SMS from this mobile number
● fdate, tdate – SMS received during this date period (from fdate; to tdate)
● date format: yy/mm/dd
● ftime, ttime – SMS received during this time period (from ftime; to ttime)
● time format: hh:mm:ss
● text – SMS received matching this text completely

Regards,
Bryon

[Bryon Davis]

Hi Nick,
Sorry, there isn’t a way to do this on the iSMS. I would check with your cellular provider, they may have some options for this.

Regards,
Bryon

[Bryon Davis]

Hi Ulrich,
For sending and receiving special characters with 7-bit ASCII, we recommend using the latest firmware v1.51.25 and select the “3GPP 23.038” ASCII 7-bit character set in the SMS Settings menu. The German characters you list are supported in this character set.

SF100 v1.51.25:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.51.25/SF100-u-v1.51.25-13Jan2014.zip

SF400 and SF800 v1.51.25:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.25/SF400-800-u-v1.51.25-13Jan2014.zip

Regards,
Bryon

[Bryon Davis]

Hi Arnd,
There currently isn’t a way to check the modem status through the API, but there is a feature request for this so it may be added to a future release.

There isn’t a way to delete the Inbox through the API either. Currently the only way to delete the Inbox is through the web menu. The size of the Inbox is managed so you shouldn’t need to delete the Inbox for space reasons.

Regards,
Bryon

[Bryon Davis]

Hi David,
I have not seen this problem before.

When it stops sending to outside carriers, it still sends across the TMobile carrier?

Are you able to get it working again after this happens? If so, how?

Regards,
Bryon

[Bryon Davis]

Sorry, we haven’t done any testing with any “SMS campaing administration software”, so I can’t say which are compatible.

[Bryon Davis]

Hi Gustavo,
The Outbox’s size is maintained by its size, not the number of messages. It would be hard to give an estimate on the number of messages, because the sizes of the messages vary and effect how many can be stored. The max Outbox size allowed is 600kb.

Regards,
Bryon

[Bryon Davis]

Hi Devon,
You could’ve also just inserted the blank compact flash into the iSMS. When the iSMS boots up it will detect the blank compact flash and automatically format and replace the needed files. But all settings will be factory default and any history and logs will be blank.

Using the multi-card card reader may allow you to recover the settings and logs, depending on how intact the original CF data is.

Regards,
Bryon

[Bryon Davis]

Hi Devon,
It sounds like the SF800 isn’t getting far enough into its boot where it would recognize the reset button being held and perform the factory default. The best course of action would be to create a case at support.multitech.com, they will be able to follow up better on troubleshooting this problem.

Regards,
Bryon

[Bryon Davis]

Sorry, nothing new to report on the message delivery feature.

[Bryon Davis]

Hi Stuart,
I tested the Date Configuration feature, and it appears to only change the date configuration for the web menus. I’ll create a bug report for this so it can be fixed in a future release.

We apologize for the inconvenience.

Regards,
Bryon

[Bryon Davis]

Hi Stuart,
There is a “Date Configuration” setting in the SMS Settings menu that will change this.

Regards,
Bryon

[Bryon Davis]

Hi Ronny,
It appears the SF100 isn’t able to find the cellular network. A signal strength of 99 means the radio isn’t connected.

Check to make sure the antenna is connected correctly and that you can receive a signal from the SF100 location.

You should also check the frequency band the radio is using with a AT+WMBS=? command, and then verify that it is set to use the same frequency as your cellular network. I believe the Philippines use 900/1800 frequencies.

Here are the AT+WMBS values:

<Band> Frequency Band Configuration
0 mono-band mode 850 MHz
1 mono-band mode 900 extended MHz (900E)
2 mono-band mode 1800 MHz
3 mono-band mode 1900 MHz
4 dual-band mode 850/1900 MHz
5 dual-band mode 900E (extended) /1800 MHz
6 dual-band mode 900E (extended) /1900 MHz
7 quad-band mode 850/900E (extended)/1800/1900 MHz

Also verify that the towers near you support 2G. The SF100 only supports 2G.

Regards,
Bryon

[Bryon Davis]

Hi Stuart,
AT Commands can only be sent to a modem using the TCP Connection feature, which directly connects you to the modem. When the TCP connection to a modem is active, the iSMS has no control over that modem until the TCP connection is ended, so all messages would have to be manually sent and received using AT commands while the connection is active.

You can test this feature by opening a telnet session on the iSMS to port 5000. Port 5000 is for modem 1, up to port 5007 for modem 8 (on a SF800).

Regards,
Bryon

[Bryon Davis]

Hi Stuart,
The current wireless modem on the iSMS is the GPRS G2 Modem. Below is a link to document that covers this modem’s AT commands. The previous F4 modem also uses most of the same AT commands.

http://www.multitech.com/en_US/DOCUMENTS/Collateral/manuals/S000463F.pdf

Regards,
Bryon

[Bryon Davis]

Hi Stuart,
Thanks for the update. Glad to here it’s working now.

Regards,
Bryon

[Bryon Davis]

What are the versions of Apache and iSMS are you using?

Perhaps there has been a change made in the Apache version you are using. I can try testing it and see if it works for me.

[Bryon Davis]

Here’s an example of the XML data that is sent:

XMLDATA=<?xml version=”1.0″ encoding=”ISO-8859-1″?>
<Response>
<Msg_Count>1</Msg_Count>
<MessageNotification>
<Message_Index>1</Message_Index>
<ModemNumber>1</ModemNumber>
<SenderNumber>17637425555</SenderNumber>
<Date>13/09/03</Date>
<Time>16:16:01</Time>
<EncodingFlag>ASCII</EncodingFlag>
<Message>TestSMS00002</Message>
</MessageNotification>
</Response>

Wireshark IP captures would show you the exact format that was sent and whether the message’s text was included.

[Bryon Davis]

We have some sample code on the FTP site. Try using the PHP sample code as a test. It is a simple program that uses Apache. The HowTo.rtf file explains how to use the sample code.

The PHP sample code it in the folder at the link below:
https://webfiles.multitech.com/engineering/sample-code/sms-finder/PHP/

[Bryon Davis]

Hi Stuart,
It’s difficult to tell with the limited information. It appears from the logs that the message Twentyone was received and delivered.

Is this a new setup? Has it ever successfully delivered a message to your Non-polling server?

Regards,
Bryon

[Bryon Davis]

Hi Laurent,
The current wireless modem on the iSMS is the GPRS G2 Modem. Below is a link to document that covers this modem’s AT commands. The previous F4 modem also uses most of the same AT commands.

http://www.multitech.com/en_US/DOCUMENTS/Collateral/manuals/S000463F.pdf

Regards,
Bryon

[Bryon Davis]

Hi Thomas,
It’s true that the current firmware doesn’t allow blank sms messages, outgoing or incoming. Another potential problem for you is incoming MMS messages. These aren’t currently supported and aren’t reported either.

I will put in a bug report for the blank incoming sms messages problem, so this can be fixed in a future patch.

Regards,
Bryon

[Bryon Davis]

Hi Thomas,
If you want to follow up on the non-polling issue, please create a case in our support portal at support.multitech.com. It will be much easier for us to troubleshoot it there.

A couple of notes. The SMS Setting menu’s Extended ASCII and Unicode selections as the default encoding won’t effect the encoding of received sms messages. The encoding is controlled by the sender. The UTF-8 setting in the HTTP API Configuration is for receiving API requests. The non-polling posts are still the ISO-8859-1 character set. Sorry, the menu setting wasn’t clear on this.

Regards,
Bryon

[Author]

Posts