Search Results for 'SMS API'

[Bryon Davis]

Hi Steven,

The C# examples for the iSMS API are at the link below:

https://webfiles.multitech.com/engineering/sample-code/sms-finder/c-sharp/

Regards,

Bryon

[Steven McNeese]

I have seen reference in some of the forum posts to C# examples for integrating with the iSMS server. I have not been able to locate these. Can you some provide a link?

Steve

[Gustavo Santos]

Its working via administration page. What´s the directions to send multipart sms like that but via API?

[Edmundo Sanchez]

Please Help

I configure Non Polling with my test server and it works, but when i configure isms to send post message to my production server, it does not work.

Both servers responds with HTTP/1.1 200 OK.

Both says: NON-POLLING RECEIVE API DELIVERY FAILED: Error reading response from server.

But with the test server, says after the past error: Delivery Successfull, but with my production server says:

recvlivelog: HTTP NON-POLLING RECEIVE API DELIVERY FAILED: Failed to connect to server.

recvlivelog: Non-Polling Post Failed to Send. Will try again later

Both servers proceses the message, the difference is that isms continue sending the message with my production server.

Any help would be apreciate.

Sorry for my english

Edmundo

[Brian]

Hi Byron,

Thanks for the reply.

I’m mostly interested in fixing some long standing problems with the firmware.

I know you’ve made improvements to the firmware for these devices, but I’d like to create a stripped down version of the firmware without the Admin UI & features which I don’t need. I’d like to build a RESTful JSON API on top of these modems which is more compatible with my systems level integration that I’m doing.

The MultiConnect OCG is nice product but I’ve already purchased the SF100 & SF800 equipment a few years ago. That’s probably not going to help my situation unless I’m willing to spend more money. The SF800 over $1,000.

I’d really appreciate it if you could put some effort finding the legal status of the firmware’s compliance with the GPL.

# uname -a

Linux MultiModemiSMS 2.4.27-uc1 #85 Thu Nov 18 10:58:21 CST 2010 armv5b unknown



# cat /proc/version

Linux version 2.4.27-uc1 (rcrogers@ubudev) (gcc version 3.3.6) #85 Thu Nov 18 10:58:21 CST 2010



# busybox --help

BusyBox v1.00 (2010.11.18-17:03+0000) multi-call binary

I’m not looking to cause trouble but if MultiTech is distributing GPL’ed code, MultiTech should be distributing the source along with it; otherwise, I think it’s considered a violation of the GPL.

Ultimately don’t want it to come down to reporting a potential GPL violation … please understand, I just simply want the source code that’s being used so I can make my own modifications and improvements.

Thanks,

Brian

[Brian]

Hello,

I have an SF800-G and an SF100-G.

I’d like to write my own firmware for these devices.

As I understand it, the iSMS firmware runs a small linux distro / busybox on an Intel XScale processor.

Ultimately, I’d like to change the API; where would I be able to download the build-toolchain for these devices to create my own firmware?

Thanks,

Brian

[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

[Hien Pham]

Hi,

I have read the API document, and not found any API to notify the application the status of the SMS sent out.

Do we have such function on the API, or we have to use the query API to get the status of the SMS sent out?

Regards,

Hien Pham

[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

[Trevor Benedict]

TCP Receive API

I have it setup as Non-Polling and no auth.

I can receive the messages just fine.

The issue is that the iSMS wants a “ok” response back.

There in no information in the PDF’s on how to do this.

We have tired all sorts of strings being sent back to the iSMS, and nothing works.

What do we need to send back to the iSMS device?

[Erik Dunder]

When sending sms via iSMS (TCP API or webgui) that contains “[” or “]” they are converted to blank space.

Nothing major but a little disturbing since it brakes the naming scheme of our monitors that we are using iSMS to send alerts about.

[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

[Jeffrey Dean]

I have a system monitoring software what uses CRLF between line elements in a text block in the GET request it sends to the API. On our iSMS SF100-G this results in a duplicate message being sent. Is this a “feature” and if so is it a feature that can be “disabled” or the %0D ignored by the unit 😉

Thanks

Jeff

[Kamran Rana]

Hi Darrik

thanks your links help to solve my problem

I just added %20 to each word token where a space was needed before composing the sms message

best regards

kamran

[Darrik Spaude]

I’d still like to see the actual string that is received by the iSMS. In the world of URLs, a plus (+) is used in place of a space. I’m assuming you need to encode your message before sending it to the iSMS, but it would be nice to know what the iSMS is actually receiving because then we could determine why it falls over.

See section 2.2 of RFC 1738:

http://www.ietf.org/rfc/rfc1738.txt

This may also be of use:

http://www.w3schools.com/tags/ref_urlencode.asp

[Kamran Rana]

Hi Darrik

urlstring:=’http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&enc=0&priority=2&to=’+mobilenumber+’&text=’+sms_text;

where mobilenumber:='”07516171888″‘;

data1:=fieldofchar1;

data2:=fieldofchar2;

where sms_text:=data1+data2;

from what i can work out when composing the full message it falls over when it comes across any spaces

if data1:= ‘abcde’ and data2:=’it a fine day’

where sms_text:=data1+data2 — falls over

where sms_text:=data1 works ok

thanks

kamran

[Darrik Spaude]

Kamran,

What is the actual URL that is being sent to the iSMS?

[Kamran Rana]

hi

I have a number of database fields that contain text that will be used to build up the message text before being sent.

eg.

data1:=’hello’

data2:=’are’

data3:=’you’

data3:=’there’

sms_text=data1+data2+data3+data4

and used with a get url command

eg. ‘http://192………..+’&text=’+sms_text;

the above does not work ? it only works with data1 on its own but when i try to add more eg data2+data3+data4 it does not work.

There is clearly a formatting issue of some sort?

The API is not interpreting the joined data ?

Thanks

Kamran

[Brian Nørgaard]

Hi if i send sms from the web site (Encoding Type)unicode and select language any i can send danish (æøå). But if i want to send this with the API. I can’t get i working

Sending:

http://192.168.0.4:81/sendmsg?user=bn&passwd=xxxxxx&cat=1&enc=2&to=”11111111″&text=test-æ-ø-å

[Kamran Rana]

Hi

sms shows in inbox(isms modem) but does not get sent to the mobile phone?

CODE string:

‘http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&to=”7516160222″&text=HELLO2’;

string sent using a get command

OUTPUT log:

Jan 1 19:12:57 boa[6823]: httplivelog: HTTP API To MultiModem iSMS

GET /sendmsg?user=admin&passwd=admin&cat=1&to=”7516160222″&text=HELLO2 HTTP/1.1

Host: 192.168.2.1:81

User-Agent: /nsoftware IPWorks HTTP/S Component – http://www.nsoftware.com

Connection: close

Jan 1 19:12:57 boa[6823]: httplivelog: MultiModem iSMS To HTTP API

HTTP/1.0 200 OK

ID: 2

why is message not getting to the phone?

have I missed something?

best regards

kamran

[Ricardo]

Thanks Bryon

I was wondering how safe it is to upgrade to this version, I have three independent Multitech iSMS 800g and they send about 2.5k – 3.5k sms/day each

But lately there has been a lot of sms lost, some just stay on Status: 3, that’s why we are looking forward to update the firmware, looking for a better performance

They all have firmware: SF400-800-u-v.147-18Nov2010.zip

We use the TCP send API and receive API

I hope we can fix this out

Regards Ricardo

[Christopher Rivera]

I’m curious to know how many simultaenous users can be logged into a box?

Right now I’m using 2 users to access the server, 1 SMS user for using the HTTP SMS API, and the main admin account to simulate web logins for pulling other data from the each of the SMS boxes.

I noticed that if I log into the server, using the admin account, it will occasionally tell me that it has logged out the previous user.

[Bryon Davis]

Hi Tyler,

Sorry, right now we don’t have any special support for VCARD.

Regards,

Bryon

[Bryon Davis]

Hi Keneth,

The ISO-8859-1 option in “SMS Settings” makes to default encoding Extended ASCII, which has problems as described above. Many providers don’t accept Extended ASCII (8bit GSM) from outside of their network.

We are looking into this problem, you could try Unicode in the mean time and see if that helps.

Regards,

Bryon

[Bryon Davis]

Hi Brian,

As mentioned previously, there is sometimes problems sending Extended ASCII between different providers. We are looking into this. It appears many providers won’t accept Extended ASCII (8 bit GSM) from outside of their network.

You can try Unicode and see if that helps.

Regards,

Bryon

[Tyler Yip]

Can the APIs be used to send message types other than SMS:TEXT, specifically SMS:VCARD?

[Kenneth Karlsson]

Hi Bryon

Do i miss some settings on my box ? i only seem to be able to select ISO-8859-1 setting. And when selected we get “unsupported format” on our phones.

I tried today with this:

http://192.168.1.211:81/sendmsg?user=admin&passwd=admin&cat=1&to=20180885&text=This%20is%20a%20test%20message%C6%D8%C5%E5%E6%F8.

The %C6%D8%C5%E5%E6%F8 part should give danish chars, bu no luck !

Kenneth

[Bryon Davis]

Hi Christophe,

I did some testing with two PCs sending sendmsg requests simultaneously. The iSMS accepted the requests from both PCs simultaneously and then sent the SMS messages. This was true for HTTP and TCP.

All requests are put in a queue and processed individually. The sending queue is fairly large, I don’t have exact numbers of the maximum on hand, but I’ve had over 3,000 jobs in the queue in my testing.

There is no real difference to the iSMS whether TCP or HTTP is used. It depends on your preference when programming the send API applications. You may prefer the support certain languages have for HTTP or TCP.

Regards,

Bryon

[Bryon Davis]

Hi Kenneth,

We are still looking into this problem.

For now I would suggest try using Unicode to send messages with special characters.

Sorry for the inconvenience.

Regards,

Bryon

[Bryon Davis]

Hi Olav,

The sending queue is fairly large, it can handle thousands of pending jobs. I don’t currently have an exact number, but I’ve seen over 3,000 in my testing.

As far as monitoring the sending queue, you have a few commands. When you send a message using the API sendmsg request, the iSMS responds with a Message ID number that you can then use to send a querymsg request to get the status of that sent message. In the newer firmware (v1.49i), there is also a queryjobs request to get the current number of pending jobs through the API. The queryjobs can limit the reponse to all jobs, high priority, normal priority, or low priority jobs.

Regards,

Bryon