Search Results for 'SMS API'

[Bryon Davis]

HI Christophe,

Which problem are you referring to? There were are few mentioned in this topic.

If you’re are referring to the original issue of buffering incoming non-polling messages when the API server is down, this is fixed in the v1.49i. You can find this at the links below. Changes and upgrade instructions are in the readme file.

SF100:

https://webfiles.multitech.com/../../engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.49i/SF100-u-v1.49i-13Oct2011.zip

SF400 and SF800:

https://webfiles.multitech.com/../../engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.49i/SF400-800-u-v1.49i-13Oct2011.zip

Regards,

Bryon

[Kenneth Karlsson]

Hi there

Facing similar problem.

Need danish chars, when i enable EXTENDED ASCII, my phone says “message format not supported”. I then click it off, and from the web-interface i can send with ÅÆ but not Ø.

Also, when i try sending with TCP API, i can not send the danish chars.

The enc=x paramateres seems not to work ?!

Hope to find a solution, the box is nice, but as it is right now, it is no good here in DK !

Kenneth

[Olav Langeland]

Hi, I am considering to use the iSMS server for our monitoring solution (soon PRTG from Paessler). I was looking for more information abou the queue management but have only found the info about API to query. Looking mainly for details about how large the queue is, info about how the priorities work.

Any help appreciated.

[Adam Goldrick]

Wondering if some one has done this.

I have a product that monitors and when something goes wrong it runs a java script that returns two variables

Phone number (smsReceiver) and a message (smsBody).

I need to get these SMS’ed.

What I can work out, is program does the folowing.

---

//variables defined here

var smsReceiver = [MobileNumber];

var smsBody = “”The Service ” + [Title] + ” is ” + [ServiceQualityLabel] + “. Time of event: ” + [ServerTime] + “.””;

//external batch file defined here

//this batch script should have two parameters: a telephone number and a message body

var batFile = “C:NotificationScript.bat”

//execution of external bat file

Packages.java.lang.Runtime.getRuntime().exec(batFile + ” ” + smsReceiver + ” ” + smsBody);

---

What I don’t have is that bat file (NotificationScript.bat) that takes those parameters and sends it to the iSMS.

I know I can use the http send API, I am just not a scripting person to write that code or don’t even know if I need aditional software like wget or curl (couldn’t get them to work anyway).

Then it got me thinking..

can it be sent directly by scripting something different then calling a bat file, like using java directly, internet search led me to this

response.sendRedirect(“http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&to=” + smsReceiver + “&text=” + smsBody)

I just don’t know what the “Packages.java.lang.Runtime.getRuntime().exec” or “response.sendRedirect” mean (again not a scripting person.

Anyone?

[Christophe NGUYEN]

Hi,

We are about to buy the SF100 iSMS device, and were wondering how it was handling simultaneous requests to send SMS from 2 application on 2 differents PCs on the LAN.

How does it handle simultanenous request

– with HTTP API

– with TCP API

Is there a queuing system which guarantees that every single SMS send request will be processed individually one by one or are SMS Send request rejected if another one is in progress and so the client applications need to handle its own ‘retries’ ?

If there is a queues, does it have a maximum size ?

Also, what are the main advantages/disadvantages between HTTP API and TCP API ?

Regards,

Christophe.

[Bryon Davis]

Hi Brian,

In my testing I’ve notice that not all providers accept GSM encoding, which is used by the iSMS Extended ASCII. I mostly see this when sending outside my SIM’s provider.

Check the Outbox and see if the message shows up there. You can also check Statistics & Logs–>Log Traces–>Send API Status Log and SMS Live Log. These should show whether the sms was sent.

Also check in the inbox for a message stating the sms was rejected for invalid characters.

ASCII is more widely accepted when sending between providers, which uses PCCP437. Unicode is also another option.

If this doesn’t appear to be the case for your failure, I recommend creating a case in our support portal at support.multitech.com.

Regards,

Bryon

[Brian Nørgaard]

Hi

I have make some code to the iSMS 100, and want to send SMS with Extended ASCII, because i need special charater (ø).

If i send normal it’s ok:

http://172.16.1.58:89/sendmsg?user=admin&passwd=admin&cat=1&enc=0&to=”xxxxxxxx”&text=test

But when i change “enc=1” no SMS is send.

Any idee

/Brian

[mohammad Siddiqui]

Hi,

I’m facing problem to receive unread Messages through API, I have sent 2 messages from my cell and received that message through API after 20 minutes, then send more 2 messages from my cell and received these that messages after 30 minutes I thought might be server is responding slow but now I’m unable to receive more messages either I have sent few more messages from my cell for testing purpose .

Here is my code could you help me out… What s wrong in my code or command

URLAddress = “http://192.168.71.39:81/recvmsg?user=admin&passwd=admin”

oHTTP = CREATEOBJECT(‘MSXML2.ServerXMLHTTP’)

oHTTP.Open(“GET”, URLAddress, .f.)

oHTTP.send

IF oHttp.status = 200

CheckMSG = oHTTP.Responsexml.SelectSingleNode(“//Unread_Available”).text

IF VAL(CheckMSG) =<0

MESSAGEBOX(“No New Messages are available .”,0,”System Message”)

RETURN .f.

ELSE

cXML = oHttp.responseXML.xml

STRTOFILE(cXML,”SMSRec.xml”)

XMLTOCURSOR(“SMSRec.xml”,”SMSRec”,512)

ENDIF

ELSE

MESSAGEBOX (” SMS Server is Not Responding.”,0,”System Message”)

ENDIF

Thanks & Regards

[Bryon Davis]

Hi Kelly,

The iSMS can only handle 50 recipients (names, numbers, or groups) per sendmsg. If this is exceeded a 605 Recipient Overflow is returned.

Whether the modem can recover from the 612 error depends on the cause of the error. The iSMS monitors and clears memory use, which should clear almost all of the causes. It may be possible to get an unusual failure that causes memory to fill up and not get freed. At that point, a reboot would clear the condition.

Regards,

Bryon

[Bryan Tran]

Hi K,

Yes. It is in v1.47. http://www.multitech.com/en_US/SUPPORT/Families/MultiModemiSMS/firmware.aspx

Regards,

BT

[K]

Hello:

The most recent iSMS API documentation says that the XMLDATA sent in non-polling mode when a message is received has a “Response” tag as its root element. Like this:

<Response>

<MessageNofitication>blah…</MessageNotification>

</Response>

I don’t get a <Response> element as my root element – I just get the <MessageNotification> as the root element.

Is this something that changed with a newer version? I’m using v1.31.

Thank you,

K

[mohammad Siddiqui]

HI,

See my logs and guide me if any thing wrong it

Thanks

SMS Statistics *-**-*-*-*-*-*-*-**-*-**-**-*

SIM Status Disabled – No SIM

Signal Strength 26

Messages in Inbox 0

Messages Sent 0

Rate of Sent Messages 0

Rate of Received Messages 0

Triggers Statistics

Broadcast Triggers Configured 0

Broadcast Triggers Received 0

Action Triggers Received 0

Job Statistics

Entries in Outbox 1

Low Priority Jobs Queued 0

Normal Priority Jobs Queued 6

High Priority Jobs Queued 0

Jobs Distributed 0

Jobs Dispatched 0

Send API Status Log-=-=-=-=-=-=-=-

[Fri Aug 5 11:50:14 2011] : [MSG ID] : 1 [STATUS] : Request Received

[Fri Aug 5 12:15:39 2011] : [MSG ID] : 2 [STATUS] : Request Received

[Fri Aug 5 12:17:31 2011] : [MSG ID] : 3 [STATUS] : Request Received

[Fri Aug 5 12:18:20 2011] : [MSG ID] : 4 [STATUS] : Request Received

[Fri Aug 5 12:24:48 2011] : [MSG ID] : 5 [STATUS] : Request Received

[Fri Aug 5 12:27:19 2011] : [MSG ID] : 6 [STATUS] : Request Received

*-===============*==

Aug 5 09:38:08 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=17130000000&to=&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:38:08 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:41:04 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=17130000000&to=&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:41:04 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:42:16 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=1&17130000000&to=&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:42:16 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:43:14 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=1&to=17130000000&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:43:14 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:44:01 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=1&to=’17130000000’&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:44:01 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:44:27 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=1&to=”17130000000″&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:44:27 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:44:41 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&priority=1&to=”17130000000″&text=”HiKamran” HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:44:41 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:55:11 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

POST /sendmsg?user=admin&password=admin&cat=1&priority=1&to=”17130000000″&text=”HiKamran” HTTP/1.1

Connection: Keep-Alive

Content-Type: text/plain; Charset=UTF-8

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Content-Length: 107

Host: 192.168.70.29:81

http://192.168.70.29:81/sendmsg?user=admin&password=admin&cat=1&priority=1&to=”17130000000″&text=”HiKamran”GET /sendmsg?user=admin&password=admin&cat=1&priority=1&to=”17130000000″&text=”HiKamran” HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:55:11 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:58:18 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=”7130000000″&text=”HiKamran” HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:58:18 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:58:37 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin2&cat=1&to=”7130000000″&text=”HiKamran” HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:58:37 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 09:59:21 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=7130000000&text=HiKamran HTTP/1.1

Connection: Keep-Alive

Accept: */*

Accept-Language: en-us

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Host: 192.168.70.29:81

Aug 5 09:59:21 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:00:46 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=7130000000&text=HiKamran HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:00:46 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:01:20 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=”7130000000″&text=HiKamran HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:01:20 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:01:31 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=”7130000000″&text=”HiKamran” HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:01:31 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:05:24 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=%2271300000005%22&text=Hi20%Kamran HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:05:24 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:06:39 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=%2271300000005%22&text=Hi%20Kamran HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:06:39 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:11:25 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=%2271300000005%22&text=%22Hi%20Kamran%22 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:11:25 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 10:28:37 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=id HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 10:28:37 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:26:15 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=602 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:26:15 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:28:42 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=%22mResult%22 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:28:42 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:34:00 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=mResult HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:34:00 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:45:31 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=%2271300000005%22&text=Hi%20MKS HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:45:31 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:45:41 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&password=admin&cat=1&to=%227130000000%22&text=Hi%20MKS HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:45:41 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 11:50:14 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=Hi%20MKS HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 11:50:14 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 1

Aug 5 12:15:39 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=%22Hi%20MKS%22 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:15:39 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 2

Aug 5 12:17:31 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=Hi HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:17:31 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 3

Aug 5 12:18:20 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=Hi%20mks HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:18:20 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 4

Aug 5 12:24:48 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=HI%20MKS HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:24:48 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 5

Aug 5 12:27:19 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=%227130000000%22&text=Hellow HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:27:19 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 6

Aug 5 12:29:55 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=1 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:29:55 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

Aug 5 12:30:45 boa[5634]: httplivelog: HTTP API To MultiModem iSMS

GET /querymsg?user=admin&password=admin&apimsgid=%221%22 HTTP/1.1

Accept: */*

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; iOpus-Web-Automation; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C)

Host: 192.168.70.29:81

Connection: Keep-Alive

Aug 5 12:30:45 boa[5634]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

Err: 602

[mohammad Siddiqui]

Hi,

I have sent sms through HTTP Send API Request and got ID : 1 , how to resolve that problem because sms is not sending

Here is my code :

URLAddress = “http://192.168.70.29:81/sendmsg?user=admin&passwd=admin&cat=1&to=%227134400105%22&text=Hi%20MKS&#8221;

oHTTP = CreateObject(“MSXML2.XMLHTTP”)

oHTTP.Open(“GET”, URLAddress, .f.)

oHTTP.send

mResult = oHTTP.ResponseText

Please Guide me what s wrong with my code or something missing on it ?

thanks

MKS

[Bryon Davis]

Sorry, there currently isn’t a way to configure the iSMS to put a time stamp in the SMS message.

If you are sending SMS messages using the API, your API program could insert the time stamp into the message when sending the sendmsg request.

[Bryon Davis]

Hi Kelly,

If the iSMS is busy or temporarily runs out of space for another message it will return a 608.

Can you give an example of the commands you are sending to send with enc and priority?

Here is an example of a command that has both enc and priority. I tested this on v1.47 firmware.

http://192.168.2.143:81/user=admin&passwd=admin&cat=1&enc=1&priority=3&to=”7637654321″&text=”test&#8221;

You’ll need to change the port from 81 to your port, and the username and password.

Regards,

Bryon

[Ed Silent]

Hello, I’m trying to use de recvmsg command but it’s not working (I’ve got the MultiModem iSMS SF100-G), it shows the following page:

http://www.freeimagehosting.net/uploads/8317178789.png

The Receive API is configured this way:

http://www.freeimagehosting.net/uploads/40a10efa1c.png

And the Send API is configured this way:

http://www.freeimagehosting.net/uploads/5130e7d7a5.png

I’m trying to use it this way:

http://201.122.162.20:80/recvmsg?user=admin&passwd=Secret

Does anyone knows what I’m doing wrong?

Thanks for your help

PS I put this post on an incorrect forum earlier, sorry for that.

[Campbell Elder]

How would you convert these Java apps in to CDP compiled apps?

ftp://ftp.matrixelectronica.eu/MTX-Terminals/Java%20examples/

examples are for:- send a SMS when GPIO changes, PPP conection with Java APIs, GPS location procedures

They are currently for Cinterion modules.

[Jeff Blees]

Hi Alex,

Thank you for the feed back.

With regards to the iSMS server product line, we are aware of – others have requested, that we improve/expand our API command set with regards to system status, management type functions, etc.

Currently, system management and performance is performed through port 80 with a Web Browser (reviewing the contents of various menu). Currently, no changes in this area are planned.

I believe our “priority” option does not effect through put (how many messages we send per minute). We have only one send queue and the priority option helps dictate which message we should send next.

Sincerely

Jeff Blees

Engineering Technician

[Jeff Blees]

Upon receipt of the SMS from the wireless cloud, this iSMS server will try 3 times in a row to POST the message to the server. If the POST attempts are unsuccessful, the message will be placed into the Receive API Failure log and is not be re-sent / re-queued. The message is also placed in the Inbox and Received SMS trace log. The originator will have to resend once the net server is back up or the net server administrator will have to manually review the iSMS server to learn what messages came in while the net server was down.

The Polling method of Receive API was implemented to address this concern.

Sincerely

Jeff

[Campbell Elder]

How does the iSMS deal with a recipient net server failure used for the NON-Polling API solution?

Is the SMS stored and re-queued?

In event of the recipient server being unavailable before the iSMS reaches memory capacity will the iSMS stop receiving untill it can deliver the SMS?

[Ed Willson]

So this was easier than I thought. I didn’t know that when the receive API was enabled it just forwards all messages to the server listed. I was searching for the mechanism that would make the message be sent to the application. I’ll post up a sample in a couple days… It’s going well though.

Thanks,

Ed

[Randy Paries]

Brian,

Are you saying this is a new feature with the SF devices we already have?

I am lookng in the API doc and do not see any reference. This sounds like an interesting feature

Randy

[Ed Willson]

After I updated to 1.47 I had to restart the modem and wait about 10 minutes for the SIM to show as active.

[Bryon Davis]

I’m not exactly sure what you’re trying to do, but besides doing some trigger features, to run a command after a SMS you would need a program running on a PC or webserver that would use the iSMS API to receive incoming SMS, interpret the SMS and execute your command on that PC/webserver, and then send a SMS with the results using the API.

For more detailed information we would need to know more about the programming language being used and the setup.

There are some iSMS API programming examples that may be helpful on our FTP site at https://webfiles.multitech.com/engineering/sample-code/sms-finder/

[Bryon Davis]

For non-development problems, it’s best to create a case in our tech support portal at support.multitech.com.

[Darrik Spaude]

Hi,

Did you review the receive API?

http://www.multitech.net/developer/products/isms/isms-receive-api/

Do you have an example of what you tried to do (sample code)? What URI did you post to?

[Coby Hochstein]

Does anyone have example code using PHP to send a txt message to the SMS server ?

We are getting the following response :

<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>

[Jeff Blees]

Hi Kirk,

We’re sorry you didn’t get a response right away through this forum. I see that you had to open a support case through our WEB portal and were then able to close out the issue.

I just wanted to post your findings to this thread. Please Note: We added that <Response> element to our XML data structure in iSMS version 1.44. I’ll mention to the Engineer of the C# example code to update the example.

Thanks

Jeff Blees

Engineering Technician

Kirk Wrote:

Figured it out. The iSms was doing everything as configured. On my default.aspx page I had to set ValidateRequest=”false” otherwise IIS thought it was malicious code being sent and rejected the post.

Also, in the C# code sample MultiTech has this line

XmlNodeList xmlNodeList = xmlDoc.SelectNodes(“/MessageNotification”);

I couldn’t get that to work so I changed it to

XmlNodeList xmlNodeList = xmlDoc.SelectNodes(“/Response/MessageNotification”);

[Kirk Bennett]

I have the following settings and I can’t get the iSms to send out the receive Sms. Is there another setting I’m missing? I did save and restart the iSms.

Non Polling Receive API Status = checked

Protocol = HTTP

Server = 192.168.1.3

Port = 80

iSms IP = 192.168.1.20

Server Default Page = Default.aspx

Post Interval = 0

I tried both with Server Authentication and without. My test server doesn’t require Authentication on that website

[Kirk Bennett]

Maybe if was Jeff Kline. I new the Jeff part was right. I’m not having any problems. It’s working great during my testing. I just want to make sure I didn’t have to take action when it sends me the log. Is the apimsgid generation tied to the device or to the port? If I send sms out port 1 and it gets apimsgid = 1, then I send sms out port 2 (both in the same device) will it get apimsgid = 2 ? Also do I have to specify a port number when I perform a querymsg?