[Bryon Davis]

Hi Todd,

Glad you were able to fix the problem. If the Non-polling Receive API message wasn’t sent successfully then the iSMS will resend it repeatedly. Clearing the Inbox should’ve cleared this though.

Regards,

Bryon

[Bryon Davis]

Hi Kirk,

I haven’t heard of a bug like this. Most likely the year was a problem from where you were getting the date/time information, whether it was from a SNTP or from the time stamp sms message.

Regards,

Bryon

[Bryon Davis]

Hi Hien,

The MultiModem® iSMS User Guide for Administrators for Models SF100/400/800 should describe what features are available for this.

You can find the manual at the link below:

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

Regards,

Bryon

[Bryon Davis]

Hi,

You would have to send a querymsg query to get the status of a sent message.

The syntax for this is:

GET /querymsg?user=admin&passwd=admin&apimsgid=message id

Regards,

Bryon

[Bryon Davis]

Hi Adeel,

The querycount will give you the number of messages that haven’t been delivered through the Receive API. It doesn’t give you the number of messages in the Inbox.

There is no way to see the number of messages in the outbox, but you can tell how many messages have been sent since booting by the value of the msgid received when sending through the API. After boot up, the msgid starts at zero and increments for each message sent.

Regards,

Bryon

[Bryon Davis]

Hi Sando,

Sorry, it’s not currently possible to change the format of Receive API data.

Regards,

Bryon

[Bryon Davis]

The iSMS sometimes has problems with Gigabit Ethernet Switches. We suggest locking the Gigabit switches port going to the iSMS at 100mb or using a 100mb Ethernet Switch between them.

[Bryon Davis]

Hi Christian,

When you say you are unable to connect, do you mean through pings, web browse, and/or sending messages?

Was this behaving the same way with the previous firmware?

I suggest you go to support.multitech.com and create a case. We will be able to help you much quicker through a case.

Regards,

Bryon

[Bryon Davis]

Hi Bob,

We are getting closer to a fix for this. In our testing, many of the special character problems are from not using ISO-8859-1 character set when sending API requests or receiving messages from the Receive API. The current releases only support ISO-8859-1 character set and many programs automatically send UTF-8, which is similar but the special characters are handled different. We are also working on adding UTF-8 support for the API interface.

Regards,

Bryon

[Bryon Davis]

Hi Trevor,

Sorry for the delay. We looked at the code, and the OK respond should successfully end the delivery. Are you adding a carriage return and linefeed at the end? If not try OKCrLf.

Regards,

Bryon

[Bryon Davis]

Hi Trevor,

I’m looking into this, I will get back to you…

[Bryon Davis]

Hi Bob,

We’re hoping to have a fix for this a few weeks. We’re still in the process of testing at the moment.

Regards,

Bryon

[Bryon Davis]

Hi Erik,

These and some other special characters are a known problem and we are currently working a fix to better support these characters in 7 bit mode. In the mean time we recommend using Unicode if special characters are needed.

Regards,

Bryon

[Bryon Davis]

Hi Bob,

The problem with the single quotes is also part of the known problem with special characters. We are working on a fix for this and should have something fairly soon.

Regards,

Bryon

[Bryon Davis]

Hi Bob,

The problem with the single quotes is also part of the known problem with special characters. We are working on a fix for this and should have something fairly soon.

Regards,

Bryon

[Bryon Davis]

Hi JB,

The amount of emails sent for log full depends on how heavy the traffic is. It’s not unusual to see several emails a day under heavy traffic. The email full message just means it’s rotating logs files, and rather than delete the old log file, it emails them. So if you’re not concerned about checking details in the log you can just leave this off.

Regards,

Bryon

[Bryon Davis]

Hi Raj,

I’m not familiar with the Nagios SMS. How would an alert be sent from the Nagios SMS?

Would it be sending a SMS message to the SF100?

In this case a broadcast trigger might be set up to alert the group that a message was received.

Or would it be sent through an API request?

The API request would be sent through the IP network in the proper format to send an sms to the group. I’m not sure if this is possible with the Nagios.

Regards,

Bryon

[Bryon Davis]

Do you mean if a HTTP Non-polling Receive API post it sent to a SSL enable website? In that case I’m not sure, it would depend on if the website also supports HTTP without SSL.

[Bryon Davis]

Hi Bob,

There is sometimes a issue when sending Extended ASCII between different carriers. Many times another won’t accept Extended ASCII unless it’s across their own network.

There is a known issue with special characters not being handled correctly. We are currently working on firmware to correct this and handle more special characters. In the mean time you code try using Unicode.

Regards,

Bryon

[Bryon Davis]

Hi Jeff,

Sounds like you must have an older firmware. Please try the latest firmware at the links below:

SF100:

https://webfiles.multitech.com/iSMS/SF100-u-v1.50.7-14Aug2012.zip

SF400 and SF400:

https://webfiles.multitech.com/iSMS/SF400-800-u-v1.50.7-14Aug2012.zip

Regards,

Bryon

[Bryon Davis]

Hi Nan,

a. The iSMS can send and receive multiple languages using Unicode. Carriers will only support certain encodings, but most carriers support Unicode.

b. See a.

c. Yes, you can add SIMs for just the ports you want to use and disable the unused ports.

d. I don’t have a list of carriers. I know AT&T and T-Mobile work because we test with these. I believe we should work with most carriers as long as they support 2G GSM/GPRS, and the SIM are not pin enabled.

e. Yes you can specify which modem to use when sending. You will receive messages to modems based on which number they sent it to. So if you want someone to send to a certain modem, you give them the number to that modem.

Regards,

Bryon

[Bryon Davis]

Hi Robert,

Sorry, currently this can only be done from the Web Menu. The inbox and outbox sizes are managed, so they won’t grow too large.

Regards,

Bryon

[Bryon Davis]

Hi Jan,

We are aware of this problem, and are currently working on solving it. I will let you know when something is available.

Regards,

Bryon

[Bryon Davis]

Hi Tino,

Sorry for the delay. If you need more help with writing API code, you can find examples on our ftp site at https://webfiles.multitech.com/engineering/sample-code/sms-finder/

Regards,

Bryon

[Bryon Davis]

If you need immediate help, your best bet is to start a case in the support portal at support.multitech.com.

Regards,

Bryon

[Bryon Davis]

Hi Jeff,

You would probably have the best results sending messages via the API about as quick as the iSMS can send. Which is usually 6 seconds per modem. So about once every 6 seconds for a SF100, or little less than a second on a SF800. The iSMS can buffer thousands of pending messages if needed, but I have better results sending API requests timed out more.

If the network is backing up, you may have better results spacing them out more.

Regards,

Bryon

[Bryon Davis]

Hi William,

We’ll take these suggestions into consideration. Perhaps have a button that re-delivers the entire inbox to the Non-polling server when clicked.

Regards,

Bryon

[Bryon Davis]

Hi Lars,

I recommend upgrading to the v1.50.0 firmware. It fixes a bug where if the SIM filled up with messages, the modem would get in a state where it wouldn’t send, even though all the telnet port 5000 commands you mentioned looked good. Normally this messages get cleared automatically, but it was possible to sometimes get in this state.

SF100:

https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.50.0/SF100-u-v1.50.0-14May2012.zip

Regards,

Bryon

[Bryon Davis]

Hi David,

The auto reboot timer was added as a work around for problems that may occur over long periods of time, that reboots would clear. Before the iSMS is auto reboot a save to flash is done so no new setting changes, new address book, or new inbox/outbox entries are lost.

The inbox and outbox sizes are managed dynamically, and shouldn’t get so large that they use all available space.

Regards,

Bryon

[Bryon Davis]

Hi William,

Currently you can only receive new unread (unsent) messages through the polling or non-polling receive API. We are looking into adding the option to retrieve read messages using the polling method.

Regards,

Bryon

[Author]

Posts