Hi Gustavo,
In the APi text use %0D for carriage return and %0A for Linefeed.
You should also have the ASCII 7-Bit Character Set configured as “3GPP 23.038” in the SMS Settings menu. There is currently a bug that prevents carriage returns and linefeeds from working in the PCCP437 character set.
Regards,
Bryon
Hi,
I would like to know how to send a return line ( enter) via api.
For instance, with iphone I can send messages with return lines ( line break).
—————————
“how are you doing ?
I need your help”
———————–
like this.
Hi Gustavo,
I tried duplicating this problem, but it was working for me. On my SF800 I only had a SIM inserted on modem 2 and sent it messages. I was able to successfully retrieve messages using polling mode or non-polling mode.
In the SMS API menu, is the “Non-Polling Receive API Status” enabled?
Are the received messages showing up in the Inbox for modem 2?
Does the “Receive API Live Log” show anything being delivered or failures?
Regards,
Bryon
Hi,
I think I found a new bug. version from 1.51.14 up to 1.51.25.
When there´s no sim card at the first modem. The inbox messages received by the order modems are not retrivable via sms receive api.
After send a message to my cell phone and then answer , the message arrived the the modem 2 inbox, but the retrive command get´s the result below.
<Response>
<Response_End>1</Response_End>
<Unread_Available>0</Unread_Available>
<Msg_Count>00</Msg_Count>
</Response>
Hi Gerben,
Are you trying to send an action trigger? The cat=3 is for action triggers.
In my testing, I was having problems getting enc=2 (hexadecimal) to work. Do you require hexadecimal?
I was able to get enc=0 (ASCII) to work with action triggers. An example of adding an address book entry would be:
http://10.0.0.1:81/sendmsg?user=admin&passwd=OURADMINPASSWORD&cat=3&enc=0&text=ADD;Test%20Number;17775554321
Note: I added the port 81 to the “http://10.0.0.1:81” section. This port should be the same as the “HTTP Port” in the SMS API menu.
Regards,
Bryon
Thanks!
Our ISMS servers are behind a firewall but with public ip addresses. I will block access to those ports via firewall.
Thanks! i´m going to open a support ticket. we are using the lastest.
Version 1.51.25
The problem is that it´s running out of resource without during the send process.
We have 8 ISMS servers and the time that happens with the 1.51.25 varies from 10 minutos after sending process start, to a couple hours to no problem at all. 2 never had problem with this version but other 6 have this random behaviour. The version I was using before was the 1.51.14 and we had a lot less problems like that.
Hi Gustavo,
What model and firmware version are you using?
How long does it take to starting slowing down and stopping?
I haven’t seen this problem yet. You can try TCP, but I believe they are equally reliable. It sounds like your iSMS may be running out of resources over time. If you create a support case in the support.multitech.com portal, we can troubleshooting this better.
A possible work around until this gets resolved is to use the auto reboot Timer feature in the Administration->System Setup menu.
Regards,
Bryon
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
Hi,
Is it possible to reboot the ISMS server via api command? We have build a very good application with the API and we are able to detect if there´s a problem if the server take to long to answer the query status api. And most times this happens we have to reboot the iSMS.
So we would like to request a API command to reboot the server.
Another question is if the TCP API is more reliable and less isms server side resource hangry than the HTTP api?
Hi , we use in our home made system the using the polling receive API and it´s not working as expected.
We have now about 170 messages at inbox of one modem, but when we run the api , we get only the new ones.
If i send a message to one modem now, and use the api to get it, we only get the last one and not the older 170 messages. we can verify this loging into the isms server and looking at the inbox folder.
Is there a way or work around for this, or it´s a know bug or there´s more information about it that doesn´t exists at the user guide?
Our application uses the recvmsg command http api.
Thanks!
Any update on the support of sending MMS through the API/iSMS server?
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
Is it possible to include, or overide the sender name or number for an sms?
Either through the API or using AT commands?
Hi
I need to read the messages received in the modem.
Am trying to use the receive api through http:
Here is my Code in delphi using http component from nsoftware.
After building up the data I execute through a button click
and then move the data to a memo field for display.
Have I got the syntax right for the postdata
or am i missing something !. I get the following error:
“151: HTTP Protocol Error. 501 Not Implemented’ when
I click on the button to execute the code.
The only thing that shows up in the memo is:
“<HTML><HEAD><TITLE>501 Not Implemented</TITLE></HEAD><BODY><H1>501 Not
Implemented</H1>POST to non-script is not supported in Boa.</BODY></HTML>”
Any pointers would be helpful. Thank you
The Delphi Source Code:
procedure TSMSInBoxFrm.BitBtn1Click(Sender: TObject);
var urldata: TStringList;
xmlstring:String;
begin
urldata := TStringList.Create;
xmlstring:=’XMLDATA=’+’%3C%3Fxml%20version%3D%221.0%22%20′;
xmlstring:=xmlstring+’encoding%3D%22ISO-8859-1%22%3F%3E%0D%0A%3CMessageNotification%3E%0D%0A%3′;
xmlstring:=xmlstring+’CModemNumber%3E%2B2%3A19525945092%3C%2FModemNumber%3E%0D%0A%3CSenderNumber%3E%2B919844895692%3C%2F’;
xmlstring:=xmlstring+’SenderNumber%3E%0D%0A%3CDate%3E08%2F03%2F14%3C%2FDate%3E%0D%0A%3CTime%3E12%3A55%3A54%3C%2′;
xmlstring:=xmlstring+’FTime%3E%0D%0A%3CMessage%3ETest%0D%0A%0D%3C%2FMessage%3E%0D%0A%3C%2FMessageNotification%3E%0D%0A’;
urldata.Add(xmlstring);
SMSDATAhttp.ContentType := ‘application/x-www-form-urlencoded’;
Try
SMSDATAhttp.PostData:=(urldata.Text);
SMSDATAhttp.Post(‘http://192.168.2.1:80’);
except on ipwime:Exception
do begin
ShowMessage(ipwime.Message);
end;
end;
SMSInboxData.Text:=SMSDATAhttp.TransferredData;
end;
Dear Sir or Madam,
we have problems to send german “umlaute” (ÄÖÜ äöü) and german sharp s (ß) with “MultiModem iSMS”.
What’s the right configuration for our intention?
Could you please give us an example to send german national characters with HTTP API
like: http://192.168.2.1:81/sendmsg?user=bill&passwd=asdf&cat=1&enc=1&text=ÄÖÜ%C4%D6%DC
Thank you.
Best regards,
Ulrich Knoll
The iSMS hardware isn’t obsolete yet and the latest firmware was just generated yesterday. We haven’t done an official release for quite some time, but we haven’t stopped fixing bugs or adding minor features. Read the ReadMe.txt file for the 1.51.25 firmware to see if there is something new that would help:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/
Dear all,
I’m wondering if it is possible to get the current modem status via API.
We are using the iSMS system for our environment monitoring system
and it is essential to check if the modem is ready (network registration, signal quality…)
At the moment we are sending a heartbeat SMS to the modem itself and check if the send command was successful – not a very nice solution
It would also be helpful to delete the inbox via API….
Another question is, will there be a new Firmware available in the future or is this product already ‘obsolete’ (last firmware update is from 2012!)?
Thanks in advance,
Arnd
Any news? or someone that would like to sell a campaing system compatible with ISMS api?
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
Hello every one,
I have a new SF100-G (Firmware Version 1.50.7), sometimes the conection to port 80 (Web admin) and port 81 (API) broke because I use a Cisco router with Gigabit Ethernet. I resolved this shutdown the iSMS box, but right now I only get internet access to the box.
Yesterday the iSMS crashed again, I resolved login in a telnet session, and get the box online again with the command “reboot”, like a linux box.
Do you have a telnet command list supported by the SF100-G?
What command I can use to get online again the box, without reboot and not loss the inbox and outbox SMS?
Thanks very much for your time, sorry for my bad english but not is my language, gracias!
The settings is as follows:
PDU mode: Enabled
ASCII 7-bit configuration: Charset = 3GPP 23.038
Ext. ASCII 8 bit conf: Nothing selected
Unicode conf: Nothing selected
HTTP API Configuration: Preferred Char Set: UTF-8
The recived XML states “ASCII” in the EncodingFlag field. This doesn’t change regardless of the Preferred Char Set in the HTTP API Configuration.
When sending a message from the iSms Webinterface to a mobile phone the SMS is recieved correctly.
When sending a message from the iSms Webinterface to the iSms the SMS is recieved correctly.
I think the issue is related to the iSms’s generation of the XML scheme/content in th API as the modem side seems to work correctly after the firmware update and with 3GPP.
Best regards
Thomas
I was testing to see how the API handles sending text messages to invalid numbers (like a land line). I sent a test message to my office number through the API and received a success and messageID back. A short time later, I received a text message into the box from number 112-161-1611 and message that said:
“1972xxxxxxx Error Invalid Number. Please re-send using a valid 10 digit mobile number or valid short code. This is a test message that will fail”
Can you please explain where the inbound number came from? Is this a random from number assigned by the carrier we are using in the iSMS server?
Hi Steven,
In my testing the API still sends a maximum of 1232 7-bit ASCII characters in PDU. It allows me to submit a longer messages, but the message will be truncated to 1232 characters.
Regards,
Bryon
I have also tested through the API and the line feed is being stripped out on the receiving device.
It appears that the API can exceed the 1232 character limitation shown in the web admin interface. What is the message length limit for the new PDU mode?
In PDU and/or the new web interface shows a limit of 1232 characters for the message now. Why this limit? Is this just a limit for the web admin interface or is this a limit for the HTTP/TCP API as well? If this is the new limit for PDU mode, will error code 604 get returned if the message is greater than 1232?
Here is the reply from support…
1. It appears that any message sent from the admin web interface gets a MSG ID of zero and only messages sent through the HTTP or TCP API get an actual MSG ID. Is this correct?
Yes, this is correct.
2. What is the maximum value for the MSG ID and what happens when this limit is reached?
The max value of Msg ID is 4,294,967,295 (Unsigned int).
3. Does the internal counter for the MSG ID ever reset?
Yes, the MSG ID will get reset on when the iSMS is factory defaulted. The msg ids are periodically saved to flash, but some msg ids can be lost if the iSMS is reset before saving to flash.
Hi,
I have some SMS who contain binary data like this “21 8B 84 00 0C 40 00 00 8A 44 A0 A3” (i write ascii codes) and i try to read them with the HTTP API (or the TCP API) and some caracters are transformed in “20” like this “21 8B 84 20 20 40 20 20 20 44 A0 A3” by the iSMS SF400-G-EU.
Can you help me?
Hi,
Sending a multi-part message with the API is the same as sending a regular message, just with a longer text string. The iSMS will automatically split up long messages into multi-parts and send them.
See the User Guide’s Appendix A (page 76) for more information on the API.
User Guide:
http://www.multitech.com/en_US/DOCUMENTS/Collateral/manuals/S000461E.pdf
Regards,
Bryon
